[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bd29dc3e83eb8578eeb7e6c8f6c5afcf44947e7a.camel@sipsolutions.net>
Date: Sun, 12 May 2019 21:30:05 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Alex Elder <elder@...aro.org>, Kalle Valo <kvalo@...eaurora.org>
Cc: davem@...emloft.net, arnd@...db.de, bjorn.andersson@...aro.org,
ilias.apalodimas@...aro.org, andy.shevchenko@...il.com,
syadagir@...eaurora.org, mjavid@...eaurora.org,
evgreen@...omium.org, benchan@...gle.com, ejcaruso@...gle.com,
abhishek.esse@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 01/18] bitfield.h: add FIELD_MAX() and field_max()
On Sun, 2019-05-12 at 07:18 -0500, Alex Elder wrote:
> On 5/12/19 1:33 AM, Kalle Valo wrote:
> > Alex Elder <elder@...aro.org> writes:
> >
> > > Define FIELD_MAX(), which supplies the maximum value that can be
> > > represented by a field value. Define field_max() as well, to go
> > > along with the lower-case forms of the field mask functions.
> > >
> > > Signed-off-by: Alex Elder <elder@...aro.org>
> >
> > Via which tree is this going? I assume I do not have take it unless
> > someone says otherwise.
>
> Sorry about that, perhaps I should have posted it separately.
>
> I don't have an answer, but we could avoid having to coordinate
> if it went together with the rest.
It's unlikely to conflict, and I don't think anyone really thinks that
the file is "theirs" (being basically standalone), so I think you should
just take it with whatever code that needs it.
johannes
Powered by blists - more mailing lists