From: Borislav Petkov <bp@alien8.de>
To: Nick Krause <nickkrause@sympatico.ca>
Cc: "alan@lxorguk.ukuu.org.uk" <alan@lxorguk.ukuu.org.uk>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ralf@linux-mips.org" <ralf@linux-mips.org>
Subject: Re: RESEND: PATCH[60485 Bug adding breakpoint for msi-pci]
Date: Tue, 25 Mar 2014 17:10:28 +0100 [thread overview]
Message-ID: <20140325161028.GA6393@pd.tnic> (raw)
In-Reply-To: <SNT145-W659480DCC260415F2FA288A5650@phx.gbl>
On Tue, Mar 25, 2014 at 02:27:04AM +0000, Nick Krause wrote:
> > Here is my new patch as corrected for the the bug 60845.
> > https://bugzilla.kernel.org/show_bug.cgi?id=60845
> > This is the link to the bug and my comments / conversation on to get the corrections needed.
> > Below is my patch for the bug, please let me know if it gets added finally Alan .
> >
> > --- linux-3.13.6/arch/mips/pci/msi-octeon.c.orig 2014-03-22 17:32:44.762754254 -0400
> > +++ linux-3.13.6/arch/mips/pci/msi-octeon.c 2014-03-22 17:34:19.974753699 -0400
> > @@ -150,6 +150,7 @@ msi_irq_allocated:
> > msg.address_lo =
> > ((128ul << 20) + CVMX_PCI_MSI_RCV) & 0xffffffff;
> > msg.address_hi = ((128ul << 20) + CVMX_PCI_MSI_RCV)>> 32;
> > + break;
Looks like this has been fixed already: 7f02c463057fc527f52066742b84d9d89b22e83d
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
prev parent reply other threads:[~2014-03-25 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-22 21:47 PATCH[60485 Bug adding breakpoint] Nick Krause
2014-03-22 21:47 ` Nick Krause
2014-03-24 0:19 ` Nick Krause
2014-03-24 0:19 ` Nick Krause
2014-03-25 2:27 ` RESEND: PATCH[60485 Bug adding breakpoint for msi-pci] Nick Krause
2014-03-25 2:27 ` Nick Krause
2014-03-25 16:10 ` Borislav Petkov [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=20140325161028.GA6393@pd.tnic \
--to=bp@alien8.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=nickkrause@sympatico.ca \
--cc=ralf@linux-mips.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;
as well as URLs for NNTP newsgroup(s).