Re: [PATCH v1 1/3] device property: Implement device_is_big_endian()

[Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>]

On Wed, Nov 15, 2023 at 03:58:54PM +0100, Bartosz Golaszewski wrote:
> On Fri, Nov 3, 2023 at 10:08 AM Bartosz Golaszewski <brgl@xxxxxxxx> wrote:
> >
> > On Thu, Nov 2, 2023 at 4:33 PM Andy Shevchenko
> > <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote:
> > >
> > > On Thu, Oct 26, 2023 at 03:27:30PM +0300, Andy Shevchenko wrote:
> > > > On Thu, Oct 26, 2023 at 07:25:35AM +0200, Greg Kroah-Hartman wrote:
> > > > > On Wed, Oct 25, 2023 at 09:42:57PM +0300, Andy Shevchenko wrote:
> > > > > > Some users want to use the struct device pointer to see if the
> > > > > > device is big endian in terms of Open Firmware specifications,
> > > > > > i.e. if it has a "big-endian" property, or if the kernel was
> > > > > > compiled for BE *and* the device has a "native-endian" property.
> > > > > >
> > > > > > Provide inline helper for the users.
> > > > >
> > > > > Acked-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
> > > >
> > > > Thank you, Greg.
> > > >
> > > > Bart, would it be still possible to take this into next?
> > > > I would like to have at least this patch applied (with the first user)
> > > > to allow conversion of others (I have some more users of new API).
> > >
> > > Okay, seems we missed v6.7 with this, can you then prepare an immutable
> > > branch / tag with this, so other maintainers can pull in case it's needed?
> > > (I have something against tty already and perhaps something else, let's
> > >  see.)
> > >
> >
> > It arrived too late in the cycle, I needed to send my PR earlier this
> > time as I was OoO this week.
> >
> > Bart
> 
> Greg, will you take this patch through your tree and provide me with
> an immutable tag for this cycle?

Sure, let me catch up with patches after I return from Plumbers next
week.

greg k-h