[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vftz_dAEDdG8yar==BB2spBpGozqf6UNpEDr-196J9xhg@mail.gmail.com>
Date: Wed, 20 Jan 2016 21:51:21 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Måns Rullgård <mans@...sr.com>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Julian Margetson <runaway@...dw.ms>, Tejun Heo <tj@...nel.org>,
linux-ide@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] ata: sata_dwc_460ex: use "dmas" DT property to find
dma channel
On Wed, Jan 20, 2016 at 9:46 PM, Måns Rullgård <mans@...sr.com> wrote:
>>>> One comment still regarding to lli types. We can avoid warnings by
>>>> using (__force u32) in macros.
>>>
>>> But that won't give the benefits of having the types checked.
>>
>> You mean if we access the lli->field directly? I didn't quite get what
>> use case you are keeping in mind.
>
> Yes, accessing any of those fields directly with my patch gives a sparse
> warning. It's situations like these those checks are intended for.
> Defeating them seems foolish to me.
Otherwise it makes that struct looks ugly.
Why not union, though it still ugly, but less.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists