[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87r39lyvj8.fsf@kamboji.qca.qualcomm.com>
Date: Fri, 19 Aug 2016 12:09:47 +0300
From: Kalle Valo <kvalo@...eaurora.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Jakub Kicinski <jakub.kicinski@...ronome.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
David Miller <davem@...emloft.net>,
Linux Wireless List <linux-wireless@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
dinan.gunawardena@...ronome.com
Subject: Re: [RFC (v7)] add basic register-field manipulation macros
Linus Torvalds <torvalds@...ux-foundation.org> writes:
> On Thu, Aug 18, 2016 at 10:11 AM, Jakub Kicinski
> <jakub.kicinski@...ronome.com> wrote:
>> Hi!
>>
>> This is what I came up with. Changes:
>
> I can live with this, certainly. I'm not really sure how many drivers
> (or perhaps core code, for that matter) will actually start using it,
> but it at least _looks_ like a usable interface that seems to be quite
> resistant to people doing stupid things with it that would result in
> surprising results (either performance or semantics).
I'm guessing that at least in ath9k and ath10k there would be use of
these macros.
> So I'm ok with something like this coming through (for example) the
> wireless tree if the drivers there are the first ones to start using
> this.
>
> Let's see if anybody else objects.
Great, thanks for the help. Let's wait for other comments and Jakub can
then resend this without RFC. I can then take it through my tree.
--
Kalle Valo
Powered by blists - more mailing lists