lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72mG3zXA7j9KbC74hQ1BMgw713Hm3WDAcQBjKxgg0fLHeg@mail.gmail.com>
Date:   Wed, 10 Feb 2021 22:46:23 +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.

Hi Sebastian,

On Tue, Feb 9, 2021 at 10:01 AM Sebastian Andrzej Siewior
<bigeasy@...utronix.de> wrote:
>
> If I post series with more than just one patch I have a cover letter
> including:

Yeah, it is a bit confusing when reading without the context (it is
hard to keep up with everything going on unless you work full-time on
it :-)

> since this patch was small, simple and removing not required code I kept
> it out. Is this enough information for you?

If you don't mind, please add a quick sentence like (I can do it on my
side too):

    `in_interrupt()` and related context checks are being removed
    from non-core code.

Plus the tag:

    Link: https://lore.kernel.org/r/20200914204209.256266093@linutronix.de/

> The information is not wrong, it doesn't say you have to use it it your
> driver. It also does not mention that you should not. I will look into
> this.

Thanks!

Cheers,
Miguel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ