From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v1 1/3] device property: Implement device_is_big_endian()
Date: Fri, 3 Nov 2023 10:08:56 +0100 [thread overview]
Message-ID: <CAMRc=MeV9ZyOzuQFEE_duPTHYgfmr6UZU6bpjDPhrczZX4PHpg@mail.gmail.com> (raw)
In-Reply-To: <ZUPBVMdi3hcTyW2n@smile.fi.intel.com>
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
next prev parent reply other threads:[~2023-11-03 9:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 18:42 [PATCH v1 0/3] gpio: mmio: Make driver agnostic Andy Shevchenko
2023-10-25 18:42 ` [PATCH v1 1/3] device property: Implement device_is_big_endian() Andy Shevchenko
2023-10-26 5:25 ` Greg Kroah-Hartman
2023-10-26 12:27 ` Andy Shevchenko
2023-11-02 15:33 ` Andy Shevchenko
2023-11-02 15:58 ` Greg Kroah-Hartman
2023-11-02 16:47 ` Andy Shevchenko
2023-11-03 9:08 ` Bartosz Golaszewski [this message]
2023-11-15 14:58 ` Bartosz Golaszewski
2023-11-15 20:21 ` Greg Kroah-Hartman
2023-12-07 14:19 ` Andy Shevchenko
2023-12-15 14:49 ` Greg Kroah-Hartman
2023-12-15 15:08 ` Andy Shevchenko
2023-12-18 10:35 ` Bartosz Golaszewski
2023-12-18 10:55 ` Andy Shevchenko
2023-12-18 11:05 ` Bartosz Golaszewski
2023-12-18 11:18 ` Greg Kroah-Hartman
2023-12-18 12:38 ` Bartosz Golaszewski
2023-12-18 13:40 ` Andy Shevchenko
2023-12-18 11:08 ` Greg Kroah-Hartman
2023-10-25 18:42 ` [PATCH v1 2/3] gpio: mmio: Make use of device properties Andy Shevchenko
2023-10-25 18:42 ` [PATCH v1 3/3] gpio: mmio: Clean up headers Andy Shevchenko
2023-10-25 19:55 ` [PATCH v1 0/3] gpio: mmio: Make driver agnostic Linus Walleij
2023-12-18 12:43 ` Bartosz Golaszewski
[not found] ` <ZYBKn9UZIhY03DiV@smile.fi.intel.com>
2023-12-18 13:36 ` Andy Shevchenko
2023-12-18 13:37 ` Bartosz Golaszewski
2023-12-18 15:02 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMRc=MeV9ZyOzuQFEE_duPTHYgfmr6UZU6bpjDPhrczZX4PHpg@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=andriy.shevchenko@linux.intel.com \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).