From: Alexander Gordeev <agordeev@redhat.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 1/3] PCI/MSI/PPC: Remove arch_msi_check_device()
Date: Mon, 15 Sep 2014 09:34:20 +0100 [thread overview]
Message-ID: <20140915083418.GC8793@agordeev.usersys.redhat.com> (raw)
In-Reply-To: <1410748970.24738.3.camel@concordia>
On Mon, Sep 15, 2014 at 12:42:50PM +1000, Michael Ellerman wrote:
> On Sun, 2014-09-07 at 20:57 +0200, Alexander Gordeev wrote:
> > Moving MSI checks from arch_msi_check_device() function to
> > arch_setup_msi_irqs() function makes code more compact and
> > allows removing unnecessary hook arch_msi_check_device()
> > from generic MSI code.
> >
> > Cc: linuxppc-dev@lists.ozlabs.org
> > Cc: linux-pci@vger.kernel.org
> > Cc: Michael Ellerman <mpe@ellerman.id.au>
>
> I already acked the previous version, but if you didn't want it that's fine :)
I do want it, but I thought you may not agree with the new changelog ;)
> cheers
>
>
--
Regards,
Alexander Gordeev
agordeev@redhat.com
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Gordeev <agordeev@redhat.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linux-pci@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] PCI/MSI/PPC: Remove arch_msi_check_device()
Date: Mon, 15 Sep 2014 09:34:20 +0100 [thread overview]
Message-ID: <20140915083418.GC8793@agordeev.usersys.redhat.com> (raw)
In-Reply-To: <1410748970.24738.3.camel@concordia>
On Mon, Sep 15, 2014 at 12:42:50PM +1000, Michael Ellerman wrote:
> On Sun, 2014-09-07 at 20:57 +0200, Alexander Gordeev wrote:
> > Moving MSI checks from arch_msi_check_device() function to
> > arch_setup_msi_irqs() function makes code more compact and
> > allows removing unnecessary hook arch_msi_check_device()
> > from generic MSI code.
> >
> > Cc: linuxppc-dev@lists.ozlabs.org
> > Cc: linux-pci@vger.kernel.org
> > Cc: Michael Ellerman <mpe@ellerman.id.au>
>
> I already acked the previous version, but if you didn't want it that's fine :)
I do want it, but I thought you may not agree with the new changelog ;)
> cheers
>
>
--
Regards,
Alexander Gordeev
agordeev@redhat.com
next prev parent reply other threads:[~2014-09-15 8:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-07 18:57 [PATCH v2 0/3] PCI/MSI: Remove arch_msi_check_device() Alexander Gordeev
2014-09-07 18:57 ` Alexander Gordeev
2014-09-07 18:57 ` [PATCH v2 1/3] PCI/MSI/PPC: " Alexander Gordeev
2014-09-07 18:57 ` Alexander Gordeev
2014-09-15 2:42 ` Michael Ellerman
2014-09-15 2:42 ` Michael Ellerman
2014-09-15 8:34 ` Alexander Gordeev [this message]
2014-09-15 8:34 ` Alexander Gordeev
2014-09-07 18:57 ` [PATCH v2 2/3] PCI/MSI/Armada-370-xp: " Alexander Gordeev
2014-09-08 11:16 ` Jason Cooper
2014-09-15 8:36 ` Alexander Gordeev
2014-09-17 15:55 ` Jason Cooper
2014-09-17 16:17 ` Alexander Gordeev
2014-09-07 18:57 ` [PATCH v2 3/3] PCI/MSI: " Alexander Gordeev
2014-09-07 18:57 ` Alexander Gordeev
2014-09-23 20:58 ` Bjorn Helgaas
2014-09-23 20:58 ` Bjorn Helgaas
2014-09-17 15:25 ` [PATCH v2 0/3] " Thomas Petazzoni
2014-09-17 15:25 ` Thomas Petazzoni
2014-09-23 21:01 ` Bjorn Helgaas
2014-09-23 21:01 ` Bjorn Helgaas
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=20140915083418.GC8793@agordeev.usersys.redhat.com \
--to=agordeev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.