From: Ming Lei <ming.lei@redhat.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Alasdair G Kergon <agk@redhat.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Laurence Oberman <loberman@redhat.com>,
axboe@kernel.dk, linux-block@vger.kernel.org, hch@lst.de
Subject: Re: 4.16 genirq change prevents HP servers from booting [was: Re: linux-next: Signed-off-by missing for commit in the device-mapper tree]
Date: Mon, 15 Jan 2018 23:33:01 +0800 [thread overview]
Message-ID: <20180115153300.GB13816@ming.t460p> (raw)
In-Reply-To: <20180115152501.GA24239@redhat.com>
On Mon, Jan 15, 2018 at 10:25:01AM -0500, Mike Snitzer wrote:
> On Mon, Jan 15 2018 at 8:27am -0500,
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > Hi all,
> >
> > Commit
> >
> > 34e1467da673 ("Revert "genirq/affinity: assign vectors to all possible CPUs"")
> >
> > is missing a Signed-off-by from its author and committer.
> >
> > Reverts are commits as well.
>
> Right, I'm aware. I staged the tree that made some HP servers finally
> work with the latest linux-block 4.16 changes. Without thinking about
> the broader implications. Anyway, I'll drop the revert from
> linux-dm.git's 'for-next'.
>
> Because I'm confident others will hunt down the irq issues.
>
> I think Ming was looking to grab the queue mapping info and CPU related
> info from the affected server.
Hi Mike,
I have cooked a fix today, please see the following link:
https://marc.info/?l=linux-kernel&m=151601867018444&w=2
This issue is clear, and has been described in above link and the
patch. If no objection, I will prepare a formal version.
--
Ming
prev parent reply other threads:[~2018-01-15 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180116002736.4d464214@canb.auug.org.au>
2018-01-15 15:25 ` 4.16 genirq change prevents HP servers from booting [was: Re: linux-next: Signed-off-by missing for commit in the device-mapper tree] Mike Snitzer
2018-01-15 15:33 ` Ming Lei [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=20180115153300.GB13816@ming.t460p \
--to=ming.lei@redhat.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=snitzer@redhat.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