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

  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.

Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
 include/linux/property.h | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)
  

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.
> 
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
>  include/linux/property.h | 26 ++++++++++++++++++++++++++
>  1 file changed, 26 insertions(+)

Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  

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@linuxfoundation.org>

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).
  

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@linuxfoundation.org>
> 
> 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.)
  

On Thu, Nov 02, 2023 at 05:33:40PM +0200, Andy Shevchenko 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@linuxfoundation.org>
> > 
> > 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.)

After -rc1 is out, I'll look into it, can't do anything until then,
sorry...

greg k-h
  

On Thu, Nov 02, 2023 at 04:58:53PM +0100, Greg Kroah-Hartman wrote:
> On Thu, Nov 02, 2023 at 05:33:40PM +0200, Andy Shevchenko 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@linuxfoundation.org>
> > > 
> > > 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.)
> 
> After -rc1 is out, I'll look into it, can't do anything until then,
> sorry...

No problem, this is actually a great news!
  

On Thu, Nov 2, 2023 at 4:33 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> 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@linuxfoundation.org>
> >
> > 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
  

On Fri, Nov 3, 2023 at 10:08 AM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
>
> On Thu, Nov 2, 2023 at 4:33 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> 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@linuxfoundation.org>
> > >
> > > 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?

Bart
  

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@bgdev.pl> wrote:
> >
> > On Thu, Nov 2, 2023 at 4:33 PM Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> 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@linuxfoundation.org>
> > > >
> > > > 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
  

On Wed, Nov 15, 2023 at 03:21:29PM -0500, Greg Kroah-Hartman wrote:
> 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@bgdev.pl> wrote:
> > > On Thu, Nov 2, 2023 at 4:33 PM Andy Shevchenko
> > > <andriy.shevchenko@linux.intel.com> 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@linuxfoundation.org>
> > > > >
> > > > > 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.
> >
> > 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.

Hope Plumbers went well!
  

On Thu, Dec 07, 2023 at 04:19:22PM +0200, Andy Shevchenko wrote:
> On Wed, Nov 15, 2023 at 03:21:29PM -0500, Greg Kroah-Hartman wrote:
> > 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@bgdev.pl> wrote:
> > > > On Thu, Nov 2, 2023 at 4:33 PM Andy Shevchenko
> > > > <andriy.shevchenko@linux.intel.com> 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@linuxfoundation.org>
> > > > > >
> > > > > > 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.
> > >
> > > 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.
> 
> Hope Plumbers went well!

Sorry for the delay, immutable tag can be found at:
	git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git device_is_big_endian-6.8-rc1
for anyone to pull from now.

thanks,

greg k-h
  

On Fri, Dec 15, 2023 at 03:49:38PM +0100, Greg Kroah-Hartman wrote:
> On Thu, Dec 07, 2023 at 04:19:22PM +0200, Andy Shevchenko wrote:
> > On Wed, Nov 15, 2023 at 03:21:29PM -0500, Greg Kroah-Hartman wrote:
> > > 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@bgdev.pl> wrote:
> > > > > On Thu, Nov 2, 2023 at 4:33 PM Andy Shevchenko
> > > > > <andriy.shevchenko@linux.intel.com> 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:

...

> > > > > > > > Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > > > > >
> > > > > > > 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.
> > > >
> > > > 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.
> > 
> > Hope Plumbers went well!
> 
> Sorry for the delay, immutable tag can be found at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git device_is_big_endian-6.8-rc1
> for anyone to pull from now.

No problem and thank you!

Bart, can you pull that? Or should I to my tree and then push with other
GPIO patches?
  

On Fri, Dec 15, 2023 at 4:11 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
>
> On Fri, Dec 15, 2023 at 03:49:38PM +0100, Greg Kroah-Hartman wrote:
> > On Thu, Dec 07, 2023 at 04:19:22PM +0200, Andy Shevchenko wrote:
> > > On Wed, Nov 15, 2023 at 03:21:29PM -0500, Greg Kroah-Hartman wrote:
> > > > 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@bgdev.pl> wrote:
> > > > > > On Thu, Nov 2, 2023 at 4:33 PM Andy Shevchenko
> > > > > > <andriy.shevchenko@linux.intel.com> 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:
>
> ...
>
> > > > > > > > > Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > > > > > >
> > > > > > > > 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.
> > > > >
> > > > > 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.
> > >
> > > Hope Plumbers went well!
> >
> > Sorry for the delay, immutable tag can be found at:
> >       git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git device_is_big_endian-6.8-rc1
> > for anyone to pull from now.
>
> No problem and thank you!
>
> Bart, can you pull that? Or should I to my tree and then push with other
> GPIO patches?
>

Ugh, this is rebased on top of 6.7-rc3...

My tree is based on rc1, if I pull it, then it'll be a mess.

Andy: How badly do you want it in v6.8? Can this wait until after the
merge window?

Bart

> --
> With Best Regards,
> Andy Shevchenko
>
>
  

On Mon, Dec 18, 2023 at 11:35:04AM +0100, Bartosz Golaszewski wrote:
> On Fri, Dec 15, 2023 at 4:11 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Fri, Dec 15, 2023 at 03:49:38PM +0100, Greg Kroah-Hartman wrote:
> > > On Thu, Dec 07, 2023 at 04:19:22PM +0200, Andy Shevchenko wrote:
> > > > On Wed, Nov 15, 2023 at 03:21:29PM -0500, Greg Kroah-Hartman wrote:
> > > > > 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@bgdev.pl> wrote:
> > > > > > > On Thu, Nov 2, 2023 at 4:33 PM Andy Shevchenko
> > > > > > > <andriy.shevchenko@linux.intel.com> 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:

...

> > > > > > > > > > Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > > > > > > >
> > > > > > > > > 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.
> > > > > >
> > > > > > 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.
> > > >
> > > > Hope Plumbers went well!
> > >
> > > Sorry for the delay, immutable tag can be found at:
> > >       git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git device_is_big_endian-6.8-rc1
> > > for anyone to pull from now.
> >
> > No problem and thank you!
> >
> > Bart, can you pull that? Or should I to my tree and then push with other
> > GPIO patches?
> 
> Ugh, this is rebased on top of 6.7-rc3...
> 
> My tree is based on rc1, if I pull it, then it'll be a mess.

But v6.7-rc3 is something that is already in the upstream.
I don't see how it can be more "mess" with this. Whatever...

> Andy: How badly do you want it in v6.8? Can this wait until after the
> merge window?

I waited for a cycle already with this...

OTOH GPIO part is not anyhow critical from the semantic point of view.
Since the main patch is in Greg's tree I'll survive with GPIO stuff
going next cycle.
  

On Mon, Dec 18, 2023 at 11:56 AM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
>
> On Mon, Dec 18, 2023 at 11:35:04AM +0100, Bartosz Golaszewski wrote:
> > On Fri, Dec 15, 2023 at 4:11 PM Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> wrote:
> > > On Fri, Dec 15, 2023 at 03:49:38PM +0100, Greg Kroah-Hartman wrote:
> > > > On Thu, Dec 07, 2023 at 04:19:22PM +0200, Andy Shevchenko wrote:
> > > > > On Wed, Nov 15, 2023 at 03:21:29PM -0500, Greg Kroah-Hartman wrote:
> > > > > > 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@bgdev.pl> wrote:
> > > > > > > > On Thu, Nov 2, 2023 at 4:33 PM Andy Shevchenko
> > > > > > > > <andriy.shevchenko@linux.intel.com> 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:
>
> ...
>
> > > > > > > > > > > Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > > > > > > > >
> > > > > > > > > > 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.
> > > > > > >
> > > > > > > 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.
> > > > >
> > > > > Hope Plumbers went well!
> > > >
> > > > Sorry for the delay, immutable tag can be found at:
> > > >       git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git device_is_big_endian-6.8-rc1
> > > > for anyone to pull from now.
> > >
> > > No problem and thank you!
> > >
> > > Bart, can you pull that? Or should I to my tree and then push with other
> > > GPIO patches?
> >
> > Ugh, this is rebased on top of 6.7-rc3...
> >
> > My tree is based on rc1, if I pull it, then it'll be a mess.
>
> But v6.7-rc3 is something that is already in the upstream.
> I don't see how it can be more "mess" with this. Whatever...
>

My for-next branch is based on v6.7-rc1 (as it should IIUC) and if I
now pull Greg's tag, I will be sending rc1-rc3 stuff to Linus Torvalds
in addition to the GPIO changes for v6.8. I bet he will not appreciate
it.

Greg: Is it too late to have this rebased on top of v6.7-rc1 instead?

Bartosz

> > Andy: How badly do you want it in v6.8? Can this wait until after the
> > merge window?
>
> I waited for a cycle already with this...
>
> OTOH GPIO part is not anyhow critical from the semantic point of view.
> Since the main patch is in Greg's tree I'll survive with GPIO stuff
> going next cycle.
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
  

On Mon, Dec 18, 2023 at 11:35:04AM +0100, Bartosz Golaszewski wrote:
> On Fri, Dec 15, 2023 at 4:11 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> >
> > On Fri, Dec 15, 2023 at 03:49:38PM +0100, Greg Kroah-Hartman wrote:
> > > On Thu, Dec 07, 2023 at 04:19:22PM +0200, Andy Shevchenko wrote:
> > > > On Wed, Nov 15, 2023 at 03:21:29PM -0500, Greg Kroah-Hartman wrote:
> > > > > 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@bgdev.pl> wrote:
> > > > > > > On Thu, Nov 2, 2023 at 4:33 PM Andy Shevchenko
> > > > > > > <andriy.shevchenko@linux.intel.com> 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:
> >
> > ...
> >
> > > > > > > > > > Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > > > > > > >
> > > > > > > > > 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.
> > > > > >
> > > > > > 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.
> > > >
> > > > Hope Plumbers went well!
> > >
> > > Sorry for the delay, immutable tag can be found at:
> > >       git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git device_is_big_endian-6.8-rc1
> > > for anyone to pull from now.
> >
> > No problem and thank you!
> >
> > Bart, can you pull that? Or should I to my tree and then push with other
> > GPIO patches?
> >
> 
> Ugh, this is rebased on top of 6.7-rc3...
> 
> My tree is based on rc1, if I pull it, then it'll be a mess.

What would make it a "mess"?  It's all upstream already, taking a merge
from a point further in time will work just fine, git is nice :)

thanks,

greg k-h
  

On Mon, Dec 18, 2023 at 12:05:54PM +0100, Bartosz Golaszewski wrote:
> On Mon, Dec 18, 2023 at 11:56 AM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> >
> > On Mon, Dec 18, 2023 at 11:35:04AM +0100, Bartosz Golaszewski wrote:
> > > On Fri, Dec 15, 2023 at 4:11 PM Andy Shevchenko
> > > <andriy.shevchenko@linux.intel.com> wrote:
> > > > On Fri, Dec 15, 2023 at 03:49:38PM +0100, Greg Kroah-Hartman wrote:
> > > > > On Thu, Dec 07, 2023 at 04:19:22PM +0200, Andy Shevchenko wrote:
> > > > > > On Wed, Nov 15, 2023 at 03:21:29PM -0500, Greg Kroah-Hartman wrote:
> > > > > > > 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@bgdev.pl> wrote:
> > > > > > > > > On Thu, Nov 2, 2023 at 4:33 PM Andy Shevchenko
> > > > > > > > > <andriy.shevchenko@linux.intel.com> 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:
> >
> > ...
> >
> > > > > > > > > > > > Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > > > > > > > > >
> > > > > > > > > > > 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.
> > > > > > > >
> > > > > > > > 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.
> > > > > >
> > > > > > Hope Plumbers went well!
> > > > >
> > > > > Sorry for the delay, immutable tag can be found at:
> > > > >       git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git device_is_big_endian-6.8-rc1
> > > > > for anyone to pull from now.
> > > >
> > > > No problem and thank you!
> > > >
> > > > Bart, can you pull that? Or should I to my tree and then push with other
> > > > GPIO patches?
> > >
> > > Ugh, this is rebased on top of 6.7-rc3...
> > >
> > > My tree is based on rc1, if I pull it, then it'll be a mess.
> >
> > But v6.7-rc3 is something that is already in the upstream.
> > I don't see how it can be more "mess" with this. Whatever...
> >
> 
> My for-next branch is based on v6.7-rc1 (as it should IIUC) and if I
> now pull Greg's tag, I will be sending rc1-rc3 stuff to Linus Torvalds
> in addition to the GPIO changes for v6.8. I bet he will not appreciate
> it.

No, you will not be sending him -rc1-rc3 stuff at all, that's not how
git works.

Try it yourself and see.  Git does a "what's the changesets that are
in this pull request and not already in mine" when determining this.
You can see it when doing a 'git request-pull', it will only show you
the diff of what will be sent.

Also look at the 'git merge-base' output, it will show the point where
things will start to be sent, and that will not have all of the -rc1
through -rc3 changes in it.

> Greg: Is it too late to have this rebased on top of v6.7-rc1 instead?

Sorry, but yes.  But don't worry, again, git can handle all of this
easily!  Try it locally and see.  Don't fear the 'fast-forward' :)

thanks,

greg k-h
  

On Mon, Dec 18, 2023 at 12:18 PM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> On Mon, Dec 18, 2023 at 12:05:54PM +0100, Bartosz Golaszewski wrote:
> > On Mon, Dec 18, 2023 at 11:56 AM Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> wrote:
> > >
> > > On Mon, Dec 18, 2023 at 11:35:04AM +0100, Bartosz Golaszewski wrote:
> > > > On Fri, Dec 15, 2023 at 4:11 PM Andy Shevchenko
> > > > <andriy.shevchenko@linux.intel.com> wrote:
> > > > > On Fri, Dec 15, 2023 at 03:49:38PM +0100, Greg Kroah-Hartman wrote:
> > > > > > On Thu, Dec 07, 2023 at 04:19:22PM +0200, Andy Shevchenko wrote:
> > > > > > > On Wed, Nov 15, 2023 at 03:21:29PM -0500, Greg Kroah-Hartman wrote:
> > > > > > > > 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@bgdev.pl> wrote:
> > > > > > > > > > On Thu, Nov 2, 2023 at 4:33 PM Andy Shevchenko
> > > > > > > > > > <andriy.shevchenko@linux.intel.com> 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:
> > >
> > > ...
> > >
> > > > > > > > > > > > > Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > > > > > > > > > >
> > > > > > > > > > > > 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.
> > > > > > > > >
> > > > > > > > > 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.
> > > > > > >
> > > > > > > Hope Plumbers went well!
> > > > > >
> > > > > > Sorry for the delay, immutable tag can be found at:
> > > > > >       git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git device_is_big_endian-6.8-rc1
> > > > > > for anyone to pull from now.
> > > > >
> > > > > No problem and thank you!
> > > > >
> > > > > Bart, can you pull that? Or should I to my tree and then push with other
> > > > > GPIO patches?
> > > >
> > > > Ugh, this is rebased on top of 6.7-rc3...
> > > >
> > > > My tree is based on rc1, if I pull it, then it'll be a mess.
> > >
> > > But v6.7-rc3 is something that is already in the upstream.
> > > I don't see how it can be more "mess" with this. Whatever...
> > >
> >
> > My for-next branch is based on v6.7-rc1 (as it should IIUC) and if I
> > now pull Greg's tag, I will be sending rc1-rc3 stuff to Linus Torvalds
> > in addition to the GPIO changes for v6.8. I bet he will not appreciate
> > it.
>
> No, you will not be sending him -rc1-rc3 stuff at all, that's not how
> git works.
>
> Try it yourself and see.  Git does a "what's the changesets that are
> in this pull request and not already in mine" when determining this.
> You can see it when doing a 'git request-pull', it will only show you
> the diff of what will be sent.
>
> Also look at the 'git merge-base' output, it will show the point where
> things will start to be sent, and that will not have all of the -rc1
> through -rc3 changes in it.
>
> > Greg: Is it too late to have this rebased on top of v6.7-rc1 instead?
>
> Sorry, but yes.  But don't worry, again, git can handle all of this
> easily!  Try it locally and see.  Don't fear the 'fast-forward' :)
>

Sorry for the noise. I did try it locally and noticed that a bunch of
commits that were merged before rc3 moved "before it" in git log and
figured this is what the PR would look like. However the PR is correct
and I should have generated it before sending the email.

Thanks for a lesson in git.
Bartosz

> thanks,
>
> greg k-h
>
  

On Mon, Dec 18, 2023 at 01:38:18PM +0100, Bartosz Golaszewski wrote:
> On Mon, Dec 18, 2023 at 12:18 PM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Mon, Dec 18, 2023 at 12:05:54PM +0100, Bartosz Golaszewski wrote:
> > > On Mon, Dec 18, 2023 at 11:56 AM Andy Shevchenko
> > > <andriy.shevchenko@linux.intel.com> wrote:
> > > > On Mon, Dec 18, 2023 at 11:35:04AM +0100, Bartosz Golaszewski wrote:
> > > > > On Fri, Dec 15, 2023 at 4:11 PM Andy Shevchenko
> > > > > <andriy.shevchenko@linux.intel.com> wrote:

...

> > > > > Ugh, this is rebased on top of 6.7-rc3...
> > > > >
> > > > > My tree is based on rc1, if I pull it, then it'll be a mess.
> > > >
> > > > But v6.7-rc3 is something that is already in the upstream.
> > > > I don't see how it can be more "mess" with this. Whatever...
> > >
> > > My for-next branch is based on v6.7-rc1 (as it should IIUC) and if I
> > > now pull Greg's tag, I will be sending rc1-rc3 stuff to Linus Torvalds
> > > in addition to the GPIO changes for v6.8. I bet he will not appreciate
> > > it.
> >
> > No, you will not be sending him -rc1-rc3 stuff at all, that's not how
> > git works.
> >
> > Try it yourself and see.  Git does a "what's the changesets that are
> > in this pull request and not already in mine" when determining this.
> > You can see it when doing a 'git request-pull', it will only show you
> > the diff of what will be sent.
> >
> > Also look at the 'git merge-base' output, it will show the point where
> > things will start to be sent, and that will not have all of the -rc1
> > through -rc3 changes in it.
> >
> > > Greg: Is it too late to have this rebased on top of v6.7-rc1 instead?
> >
> > Sorry, but yes.  But don't worry, again, git can handle all of this
> > easily!  Try it locally and see.  Don't fear the 'fast-forward' :)
> 
> Sorry for the noise. I did try it locally and noticed that a bunch of
> commits that were merged before rc3 moved "before it" in git log and
> figured this is what the PR would look like. However the PR is correct
> and I should have generated it before sending the email.

Right.

What Linus can rant on is when one rebases his stuff on newer rcX,
the merges on contrary are pretty much okay as long as they are
justified.

> Thanks for a lesson in git.