[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72kq_d=5TvdhndP9zkyTD1pHF6WQb+qs01D68DEQH6jVjQ@mail.gmail.com>
Date: Mon, 8 Feb 2021 21:14:54 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Willy Tarreau <w@....eu>
Subject: Re: [PATCH] auxdisplay: Remove in_interrupt() usage.
On Mon, Feb 8, 2021 at 8:07 PM Sebastian Andrzej Siewior
<bigeasy@...utronix.de> wrote:
>
> Yes.
In what way?
> No. If you know the context, pass it along like this is done for
> kmalloc() for instance.
What do you mean?
> The long term plan is not make it available to
> divers (i.e. core code only where the context can not be known).
Sounds good.
Cheers,
Miguel
Powered by blists - more mailing lists