From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: xiongxin <xiongxin@kylinos.cn>,
hoan@os.amperecomputing.com, linus.walleij@linaro.org,
brgl@bgdev.pl, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@kernel.org,
Riwen Lu <luriwen@kylinos.cn>
Subject: Re: [PATCH v3] gpio: dwapb: mask/unmask IRQ when disable/enale it
Date: Tue, 19 Dec 2023 16:50:58 +0200 [thread overview]
Message-ID: <ZYGt0vbI0NHzvjod@smile.fi.intel.com> (raw)
In-Reply-To: <ZYGsRXJUcrLKEzUn@smile.fi.intel.com>
On Tue, Dec 19, 2023 at 04:44:22PM +0200, Andy Shevchenko wrote:
> On Tue, Dec 19, 2023 at 05:31:38PM +0300, Serge Semin wrote:
> > On Tue, Dec 19, 2023 at 04:17:16PM +0200, Andy Shevchenko wrote:
> > > On Tue, Dec 19, 2023 at 11:14 AM Serge Semin <fancer.lancer@gmail.com> wrote:
> > > > On Tue, Dec 19, 2023 at 09:37:51AM +0800, xiongxin wrote:
...
> > > > Also note all the tags you've already got must be preserved on the
> > > > next patch revisions. One more time:
> > >
> > > I recommend using `b4` for that.
> > >
> > > it harvests tags from the email thread, so no need to care about
> > > possible misses.
> >
> > AFAICS it doesn't pick up the tags from the previous revisions at
> > least if the new patch wasn't submitted as in-reply-to the prev one.
>
> ???
Ah, I see what you mean now. Yes, the flow I suggested has to always be
followed, gaps are not permitted.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-12-19 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 1:37 [PATCH v3] gpio: dwapb: mask/unmask IRQ when disable/enale it xiongxin
2023-12-19 9:14 ` Serge Semin
2023-12-19 14:17 ` Andy Shevchenko
2023-12-19 14:31 ` Serge Semin
2023-12-19 14:44 ` Andy Shevchenko
2023-12-19 14:50 ` Andy Shevchenko [this message]
2023-12-19 14:52 ` Serge Semin
2023-12-19 18:56 ` Konstantin Ryabitsev
2023-12-19 21:58 ` Serge Semin
2023-12-19 22:10 ` Konstantin Ryabitsev
2023-12-19 22:16 ` Serge Semin
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=ZYGt0vbI0NHzvjod@smile.fi.intel.com \
--to=andy.shevchenko@gmail.com \
--cc=brgl@bgdev.pl \
--cc=fancer.lancer@gmail.com \
--cc=hoan@os.amperecomputing.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luriwen@kylinos.cn \
--cc=stable@kernel.org \
--cc=xiongxin@kylinos.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.