From: Andrew Morton <akpm@linux-foundation.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-ide@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/2] ide: Remove in_interrupt()
Date: Thu, 19 Nov 2020 17:26:37 -0800 [thread overview]
Message-ID: <20201119172637.7e7fc6679dd5766526de27b9@linux-foundation.org> (raw)
In-Reply-To: <20201119165133.oqjnlxvcry64jjsv@linutronix.de>
On Thu, 19 Nov 2020 17:51:33 +0100 Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
> On 2020-11-13 09:25:08 [-0700], Jens Axboe wrote:
> > On 11/13/20 9:10 AM, Sebastian Andrzej Siewior wrote:
> > > In the discussion about preempt count consistency across kernel
> > > configurations:
> > >
> > > https://lore.kernel.org/r/20200914204209.256266093@linutronix.de/
> > >
> > > it was concluded that the usage of in_interrupt() and related context
> > > checks should be removed from non-core code.
> > >
> > > This ide subsystem has two in_interrupts() checks before mutex/wait-event
> > > invocations.
> >
> > Acked-by: Jens Axboe <axboe@kernel.dk>
>
> Andrew, are you okay with routing these two patches via your tree?
Sure, but I'm not subscribed to linux-ide. Please resend, cc myself
and linux-kernel?
prev parent reply other threads:[~2020-11-20 1:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 16:10 [PATCH 0/2] ide: Remove in_interrupt() Sebastian Andrzej Siewior
2020-11-13 16:10 ` [PATCH 1/2] ide/Falcon: Remove in_interrupt() usage Sebastian Andrzej Siewior
2020-11-13 16:10 ` [PATCH 2/2] ide: Remove BUG_ON(in_interrupt() || irqs_disabled()) from ide_unregister() Sebastian Andrzej Siewior
2020-11-13 16:25 ` [PATCH 0/2] ide: Remove in_interrupt() Jens Axboe
2020-11-19 16:51 ` Sebastian Andrzej Siewior
2020-11-20 1:26 ` Andrew Morton [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=20201119172637.7e7fc6679dd5766526de27b9@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bigeasy@linutronix.de \
--cc=linux-ide@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).