From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Olliver Schinagl <oliver@schinagl.nl>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Andreas Noever <andreas.noever@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>
Subject: Re: [PATCH v1 1/2] iopoll: Introduce ioreadXX_poll_timeout() macros
Date: Wed, 5 Apr 2023 14:18:06 +0300 [thread overview]
Message-ID: <ZC1Y7tk40kL6SnT7@smile.fi.intel.com> (raw)
In-Reply-To: <ZC1YXarlQKresoTv@smile.fi.intel.com>
On Wed, Apr 05, 2023 at 02:15:42PM +0300, Andy Shevchenko wrote:
> On Wed, Apr 05, 2023 at 12:41:47PM +0300, Mika Westerberg wrote:
> > On Wed, Apr 05, 2023 at 11:58:15AM +0300, Andy Shevchenko wrote:
> > > On Fri, Mar 31, 2023 at 10:12:31AM +0200, Olliver Schinagl wrote:
> > > > On 30-03-2023 16:14, Andy Shevchenko wrote:
...
> > > > But I actually have a small addendum for this series, as it will break
> > > > `drivers/net/wwan/t7xx/t7xx_dpmaif.c` due to a redefinition (yeah I know).
> > > >
> > > > So I have:
> > > > https://gitlab.com/olliver/linux/-/commit/c9e591f2dabb2dbaeceebee61fa70b70fdbffc2a
> > > > https://gitlab.com/olliver/linux/-/commit/41e0f8c08a1c55940813a240215910336ad7bec2
> > > > https://gitlab.com/olliver/linux/-/commit/f36562f09b0185d403415864ef7218b46a742cdc
> > > > https://gitlab.com/olliver/linux/-/commit/66237fd97bc42d272602b01dc0cca541c619b2be
> > > >
> > > > Which actually replaces silly calls like readx_poll_timeout(ioread32, ... .
> > > >
> > > > Do you want me to (re-?)post this as a series? I can put your thunderbolt
> > > > (and your changes here) and post as one big series (or you can do the same
> > > > obviously).
> > >
> > > I believe the best course of action is to collect this series and your fix
> > > in your hands and send it as a material for Linux WWAN subsystem with Mika's
> > > Ack (if he has no objections). That said, let's wait for Mika's answer
> > > on this.
> >
> > No objections from my side.
>
> Thank you, Mika!
>
> This implies that I stop issuing a new version and Olliver takes over.
Olliver, just note that I reduced a lot your initial patch in a sense to add
only what is close to the existing users, i.e. ioreadXX() and their atomic
versions (no be(), no _rep() variants). If you are objecting that, you need
to have yet another patch(es) to prove that there are users.
Also note, that I reordered macro appearance to be consistent with existing
schema.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-04-05 11:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 14:14 [PATCH v1 1/2] iopoll: Introduce ioreadXX_poll_timeout() macros Andy Shevchenko
2023-03-30 14:14 ` [PATCH v1 2/2] thunderbolt: Make use of ioread32_poll_timeout() Andy Shevchenko
2023-03-31 8:12 ` [PATCH v1 1/2] iopoll: Introduce ioreadXX_poll_timeout() macros Olliver Schinagl
2023-04-05 8:58 ` Andy Shevchenko
2023-04-05 9:41 ` Mika Westerberg
2023-04-05 11:15 ` Andy Shevchenko
2023-04-05 11:18 ` Andy Shevchenko [this message]
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=ZC1Y7tk40kL6SnT7@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=oliver@schinagl.nl \
/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).