public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Marc Aurèle La France" <tsi@tuyoix.net>
To: Petr Mladek <pmladek@suse.com>
Cc: John Ogness <john.ogness@linutronix.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Remove orphaned CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT
Date: Mon, 27 Mar 2023 07:16:11 -0600 (Mountain Daylight Time)	[thread overview]
Message-ID: <alpine.WNT.2.20.2303270710530.3348@CLUIJ> (raw)
In-Reply-To: <ZCF72chpZx77+lEM@alley>

[-- Attachment #1: Type: text/plain, Size: 679 bytes --]

On Mon, 27 Mar 2023, Petr Mladek wrote:
> On Tue 2023-02-21 16:08:37, Petr Mladek wrote:
>> On Mon 2023-02-20 22:10:32, Marc Aurèle La France wrote:
>>> After 93d102f094be9beab28e5afb656c188b16a3793b "printk: remove safe buffers",
>>> CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT is no longer useful.  Remove it.

>>> This change is not eligible for stable@.

>>> Please Reply-To-All.

>> Great catch!
>> Reviewed-by: Petr Mladek <pmladek@suse.com>

>> I have already sent pull request with printk changes for 6.3.
>> I am going to queue this patch either for 6.3-rc or 6.4.

> JFYI, the patch has been committed into printk/linux.git,
> branch for-6.4.

Thanks and have a great day.

Marc.

      reply	other threads:[~2023-03-27 13:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21  5:10 [PATCH] Remove orphaned CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT Marc Aurèle La France
2023-02-21  8:33 ` John Ogness
2023-02-21  8:41   ` Sergey Senozhatsky
2023-02-21 15:08 ` Petr Mladek
2023-03-27 11:19   ` Petr Mladek
2023-03-27 13:16     ` Marc Aurèle La France [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=alpine.WNT.2.20.2303270710530.3348@CLUIJ \
    --to=tsi@tuyoix.net \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.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