From: Alexander Gordeev <agordeev@redhat.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Mike Qiu <qiudayu@linux.vnet.ibm.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] irqdomain: Do not reuse existing mappings
Date: Mon, 3 Jun 2013 09:35:33 +0200 [thread overview]
Message-ID: <20130603073532.GA30878@dhcp-26-207.brq.redhat.com> (raw)
In-Reply-To: <CACxGe6uWZxb_ZeSoYDOOaA9+DqSCDd+zM8SQfpKkeiCmHoUNkA@mail.gmail.com>
On Sun, Jun 02, 2013 at 05:52:21PM +0100, Grant Likely wrote:
> On Sun, Jun 2, 2013 at 12:56 PM, Alexander Gordeev <agordeev@redhat.com> wrote:
> > On Fri, May 31, 2013 at 11:30:24PM +0100, Grant Likely wrote:
> >> On Fri, 31 May 2013 14:59:11 +0200, Alexander Gordeev <agordeev@redhat.com> wrote:
> >> What exactly is the problem that you're trying to solve with this patch?
> >> It's not clear from the description.
> >
> > Hi Grant,
> >
> > Thanks for the clarification!
> >
> > No particular problem - I just was confused with this particular behaviour
> > and failed to put RFC in subject line. Sorry for that.
>
> Hi Alexander,
>
> So there isn't an actual bug or problem that you're trying to solve?
> If you've got a problem on a real system then I'd like to know about
> it.
Well, there is a QLogic HBA chip which does not support MSI-X, but does
support multiple MSIs (I suspect there are few of them in fact). The change
I posted is part of the update (multiple MSIs enablement + qla2xxx driver
change), but the whole series is not tested and frankly, I am not sure I
ever post it. So please nevermind ;)
> g.
--
Regards,
Alexander Gordeev
agordeev@redhat.com
prev parent reply other threads:[~2013-06-03 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 12:59 Alexander Gordeev
2013-05-31 22:30 ` Grant Likely
2013-06-02 11:56 ` Alexander Gordeev
2013-06-02 16:52 ` Grant Likely
2013-06-03 7:35 ` Alexander Gordeev [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=20130603073532.GA30878@dhcp-26-207.brq.redhat.com \
--to=agordeev@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiudayu@linux.vnet.ibm.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
all inboxes | Powered by JetHome®