From: Bjorn Helgaas <helgaas@kernel.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: "Sean O. Stalley" <sean.stalley@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
David Daney <ddaney.cavm@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Rafal Milecki <zajec5@gmail.com>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"yinghai@kernel.org" <yinghai@kernel.org>,
"rajatxjain@gmail.com" <rajatxjain@gmail.com>,
"gong.chen@linux.intel.com" <gong.chen@linux.intel.com>,
David Daney <david.daney@cavium.com>
Subject: Re: [PATCH v5 0/4] PCI: Add support for PCI Enhanced Allocation "BARs"
Date: Thu, 15 Oct 2015 09:06:57 -0500 [thread overview]
Message-ID: <20151015140657.GB12958@localhost> (raw)
In-Reply-To: <561E8221.7070701@caviumnetworks.com>
On Wed, Oct 14, 2015 at 09:26:09AM -0700, David Daney wrote:
> On 10/14/2015 09:17 AM, Sean O. Stalley wrote:
> >Signed-off-by: Sean O. Stalley <sean.stalley@intel.com>
> >
>
> Thanks a lot Sean.
>
> I think you cannot SOB if the patches are not flowing through you
> (as may be the case for my two additions). Perhaps a Tested-by: or
> Acked-by: would be more appropriate.
>
> >I tested it out with the QEMU EA Patches here:
> > [https://lists.nongnu.org/archive/html/qemu-devel/2015-07/msg00348.html]
> >
> >Also, I found 1 trivial typo in the commit message of PATCH 1/4:
> > "Signed-off-by: Signed-off-by: David Daney <david.daney@cavium.com>"
>
> Aargh! I need to be more careful.
>
> In any case, what should be the next course of action?
>
> A) I receive Tested-by/Acked-by from Sean, and resend the four patches?
>
> B) Bjorn takes these as is, but fixes the headers as needed.
>
> Bjorn, what do you think?
You do not need to repost patches just to add Tested-by/Acked-by/etc.
I can also fix trivial things like your Signed-off-by typo.
Bjorn
prev parent reply other threads:[~2015-10-15 14:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 23:50 [PATCH v5 0/4] PCI: Add support for PCI Enhanced Allocation "BARs" David Daney
2015-10-06 23:50 ` [PATCH v5 1/4] PCI: Add Enhanced Allocation register entries David Daney
2015-10-20 13:12 ` Bjorn Helgaas
2015-10-06 23:50 ` [PATCH v5 2/4] PCI: Add support for Enhanced Allocation devices David Daney
2015-10-20 13:48 ` Bjorn Helgaas
2015-10-06 23:50 ` [PATCH v5 3/4] PCI: Handle IORESOURCE_PCI_FIXED when sizing and assigning resources David Daney
2015-10-20 14:04 ` Bjorn Helgaas
2015-10-06 23:50 ` [PATCH v5 4/4] PCI: Handle Enhanced Allocation (EA) capability for SRIOV devices David Daney
2015-10-07 13:44 ` [PATCH v5 0/4] PCI: Add support for PCI Enhanced Allocation "BARs" Stalley, Sean
2015-10-14 16:17 ` Sean O. Stalley
2015-10-14 16:26 ` David Daney
2015-10-15 14:06 ` Bjorn Helgaas [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=20151015140657.GB12958@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=david.daney@cavium.com \
--cc=ddaney.cavm@gmail.com \
--cc=ddaney@caviumnetworks.com \
--cc=gong.chen@linux.intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mst@redhat.com \
--cc=rajatxjain@gmail.com \
--cc=sean.stalley@intel.com \
--cc=yinghai@kernel.org \
--cc=zajec5@gmail.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;
as well as URLs for NNTP newsgroup(s).