[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z4E9I-Pe1ylet0s4@pathway.suse.cz>
Date: Fri, 10 Jan 2025 16:30:43 +0100
From: Petr Mladek <pmladek@...e.com>
To: John Ogness <john.ogness@...utronix.de>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>,
Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
Rik van Riel <riel@...riel.com>, Omar Sandoval <osandov@...a.com>
Subject: Re: [PATCH printk v1 2/2] printk: Defer legacy printing when holding
printk_cpu_sync
On Fri 2025-01-10 12:28:12, John Ogness wrote:
> Hi Petr,
>
> On 2024-12-16, Petr Mladek <pmladek@...e.com> wrote:
> > JFYI, the patchset has been committed into printk/linux.git,
> > branch for-6.14-cpu_sync-fixup.
>
> I noticed that series is not yet merged into the printk/linux.git
> "for-6.14" branch. This email is just a ping so that you do not forget
> it for the upcoming merge window. ;-)
All is fine. This patchset has been in linux-next since Dec 16.
And I am going to include it in the pull request for 6.14.
The branch "for-6.14" is intended only for simple fixes.
This patchset is committed into the separate "topic" branch
"for-6.14-cpu_sync-fixup".
Both branches are merged into "for-next" branch separately.
I am sorry for confusion but I have never merged the topic
branches into "for-<version>" ones.
Best Regards,
Petr
Powered by blists - more mailing lists