From: Neil Horman <nhorman@tuxdriver.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] x86/iommu change for v3.15
Date: Mon, 31 Mar 2014 16:29:16 -0400 [thread overview]
Message-ID: <20140331202916.GC8050@hmsreliant.think-freely.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1403312144280.14882@ionos.tec.linutronix.de>
On Mon, Mar 31, 2014 at 09:45:43PM +0200, Thomas Gleixner wrote:
> On Mon, 31 Mar 2014, Linus Torvalds wrote:
>
> > On Mon, Mar 31, 2014 at 7:49 AM, Ingo Molnar <mingo@kernel.org> wrote:
> > > Neil Horman (1):
> > > x86: Adjust irq remapping quirk for older revisions of 5500/5520 chipsets
> >
> > Before I pull this, I want somebody to double-check it:
> >
> > > - if (revision == 0x13)
> > > + if (revision < 0x13)
> > > set_irq_remapping_broken();
> >
> > This change does *not* match the comment just above it. The comment
> > talks very much about revision 13.
> >
> > So the comment should be fixed, and/or that "< 0x13" should perhaps be
> > "<= 0x13".
> >
> > Because making it "less than" simply makes no sense in light of the
> > comment. Does revision 13 suddenly work? Was that where it was fixed?
> > If so, please fix the comment.
>
> That is my bad. I applied V1 of the patch instead of V2 which had the
> <= 0x13 instead of < 0x13.
>
> Please drop the pull request for now. I'll fix it up and we resubmit.
>
> Thanks,
>
> tglx
>
>
What Thomas said. That was caught and fixed already. sorry for the noise.
Neil
prev parent reply other threads:[~2014-03-31 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 14:49 Ingo Molnar
2014-03-31 19:34 ` Linus Torvalds
2014-03-31 19:45 ` Thomas Gleixner
2014-03-31 20:29 ` Neil Horman [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=20140331202916.GC8050@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®