From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Tejun Heo <tj@kernel.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
PowerPC <linuxppc-dev@lists.ozlabs.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: boot warning
Date: Wed, 10 May 2023 13:05:15 +1000 [thread overview]
Message-ID: <20230510130515.5bd2e73e@canb.auug.org.au> (raw)
In-Reply-To: <ZFpnroBw-tJnyDbF@slm.duckdns.org>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
Hi Tejun,
On Tue, 9 May 2023 05:33:02 -1000 Tejun Heo <tj@kernel.org> wrote:
>
> On Tue, May 09, 2023 at 05:09:43PM +1000, Michael Ellerman wrote:
> > Stephen Rothwell <sfr@canb.auug.org.au> writes:
> > > Hi all,
> > >
> > > Today's qemu test boot (powerpc pseries_le_defconfig) produced this
> > > warning:
> > >
> > > [ 2.048588][ T1] ipr: IBM Power RAID SCSI Device Driver version: 2.6.4 (March 14, 2017)
> > > [ 2.051560][ T1] ------------[ cut here ]------------
> > > [ 2.052297][ T1] WARNING: CPU: 0 PID: 1 at kernel/workqueue.c:5925 workqueue_sysfs_register+0x20/0x1f0
> >
> > Caused by 59709bb84c22 scsi: Use alloc_ordered_workqueue() to create ordered workqueues.
>
> The patch is already dropped. It was applied only for a short window
> yesterday. Should be okay now.
Confirmed, the warning is gone.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-05-10 3:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 2:24 linux-next: boot warning Stephen Rothwell
2023-05-09 7:09 ` Michael Ellerman
2023-05-09 15:33 ` Tejun Heo
2023-05-10 3:05 ` Stephen Rothwell [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=20230510130515.5bd2e73e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=James.Bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=martin.petersen@oracle.com \
--cc=mpe@ellerman.id.au \
--cc=tj@kernel.org \
/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