From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Luis Chamberlain <mcgrof@kernel•org>
Cc: "Eric W. Biederman" <ebiederm@xmission•com>,
Tong Zhang <ztong0001@gmail•com>,
Andrew Morton <akpm@linux-foundation•org>,
Linus Torvalds <torvalds@linux-foundation•org>,
Domenico Andreoli <domenico.andreoli@linux•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: boottime warning from todays linux-next
Date: Fri, 11 Feb 2022 18:46:47 +1100 [thread overview]
Message-ID: <20220211184647.0a62dad4@canb.auug.org.au> (raw)
In-Reply-To: <YgW+DopXpFNZTj4k@bombadil.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
Hi Luis,
On Thu, 10 Feb 2022 17:38:22 -0800 Luis Chamberlain <mcgrof@kernel•org> wrote:
>
> On Fri, Feb 11, 2022 at 12:33:36PM +1100, Stephen Rothwell wrote:
> >
> > Thanks for noticing that. I have removed the old version from my copy
> > of mmotm today.
>
> And ... does that fix your boot?
Yes, the messages are all gone.
Thanks again.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-02-11 7:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 7:43 linux-next: boottime warning from todays linux-next Stephen Rothwell
2022-02-10 8:33 ` Stephen Rothwell
2022-02-10 10:41 ` Stephen Rothwell
2022-02-10 11:29 ` Stephen Rothwell
2022-02-10 23:19 ` Luis Chamberlain
2022-02-11 1:33 ` Stephen Rothwell
2022-02-11 1:38 ` Luis Chamberlain
2022-02-11 7:46 ` Stephen Rothwell [this message]
2022-02-11 18:51 ` Luis Chamberlain
2022-02-11 19:12 ` Tong Zhang
2022-02-10 18:06 ` Domenico Andreoli
2022-02-10 23:35 ` Tong Zhang
2022-02-11 1:43 ` Stephen Rothwell
2022-02-11 17:36 ` Tong Zhang
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=20220211184647.0a62dad4@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=domenico.andreoli@linux$(echo .)com \
--cc=ebiederm@xmission$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mcgrof@kernel$(echo .)org \
--cc=torvalds@linux-foundation$(echo .)org \
--cc=ztong0001@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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