From: Greg KH <gregkh@linuxfoundation.org>
To: "tiantao (H)" <tiantao6@huawei.com>
Cc: Tian Tao <tiantao6@hisilicon.com>,
hvaibhav.linux@gmail.com, johan@kernel.org, elder@kernel.org,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: greybus: move to use request_irq by IRQF_NO_AUTOEN flag
Date: Wed, 7 Apr 2021 10:40:53 +0200 [thread overview]
Message-ID: <YG1wFcQvKmYsziLt@kroah.com> (raw)
In-Reply-To: <5126cb93-4227-8a0f-1421-7685ade4b2e2@huawei.com>
On Wed, Apr 07, 2021 at 04:29:59PM +0800, tiantao (H) wrote:
>
> 在 2021/4/7 16:22, Greg KH 写道:
> > On Wed, Apr 07, 2021 at 02:50:03PM +0800, Tian Tao wrote:
> > > disable_irq() after request_irq() still has a time gap in which
> > > interrupts can come. request_irq() with IRQF_NO_AUTOEN flag will
> > > disable IRQ auto-enable because of requesting.
> > >
> > > this patch is made base on "add IRQF_NO_AUTOEN for request_irq" which
> > > is being merged: https://lore.kernel.org/patchwork/patch/1388765/
> > Can you wait until that is merged before sending this out to us as we
> > can't do anything until then.
>
> this is already in linux-next.git.
>
> cbe16f3 genirq: Add IRQF_NO_AUTOEN for request_irq/nmi()
That's great, but note that linux-next is a combined tree of all
subsystem trees. It's impossible for a subsystem tree to include
linux-next :)
So how about we wait until this gets into Linus's tree so that we do not
all suddenly get problems in our individual subsystem trees.
thanks,
greg k-h
next prev parent reply other threads:[~2021-04-07 8:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 6:50 [PATCH] staging: greybus: move to use request_irq by IRQF_NO_AUTOEN flag Tian Tao
2021-04-07 8:22 ` Greg KH
2021-04-07 8:29 ` tiantao (H)
2021-04-07 8:40 ` Greg KH [this message]
2021-04-07 8:43 ` tiantao (H)
2021-04-08 0:51 ` tiantao (H)
2021-04-08 6:25 ` Greg KH
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=YG1wFcQvKmYsziLt@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=elder@kernel.org \
--cc=greybus-dev@lists.linaro.org \
--cc=hvaibhav.linux@gmail.com \
--cc=johan@kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=tiantao6@hisilicon.com \
--cc=tiantao6@huawei.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