From: Bjorn Helgaas <helgaas@kernel.org>
To: "Sergio Miguéns Iglesias" <lonyelon@gmail.com>
Cc: konrad.wilk@oracle.com, boris.ostrovsky@oracle.com,
jgross@suse.com, sstabellini@kernel.org, bhelgaas@google.com,
xen-devel@lists.xenproject.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Sergio Miguéns Iglesias" <sergio@lony.xyz>
Subject: Re: [PATCH v2] xen/pcifront: Removed unnecessary __ref annotation
Date: Mon, 30 Aug 2021 14:18:10 -0500 [thread overview]
Message-ID: <20210830191810.GA13209@bjorn-Precision-5520> (raw)
In-Reply-To: <20210830201426.g2vaxh6chqnprual@archlap>
On Mon, Aug 30, 2021 at 10:14:26PM +0200, Sergio Miguéns Iglesias wrote:
> Thanks again for you answers!
> I am lerning a lot from your replys and I really appreciate it. Should I
> make a v3 patch and split that one into 2 different patches or would it
> be confusing?
>
> I don't want to take more of your time with poor patches so I don't know
> if I should resend this one.
If it's already applied, it doesn't matter for this case. But in this
situation I would generally post a v3 incorporating the feedback. To
be respectful of reviewers' time, try to avoid posting more than one
or two revisions per week. As long as you tag reposts appropriately
with v2, v3, etc (as you did), there's no confusion.
It's nice if you include a note about what changed between v1 and v2
in the cover letter or below the "---" line as was done here:
https://lore.kernel.org/linux-pci/8f9a13ac-8ab1-15ac-06cb-c131b488a36f@siemens.com/
next prev parent reply other threads:[~2021-08-30 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 17:53 Sergio Miguéns Iglesias
2021-08-30 16:12 ` Juergen Gross
2021-08-30 16:29 ` Bjorn Helgaas
2021-08-30 20:14 ` Sergio Miguéns Iglesias
2021-08-30 19:18 ` Bjorn Helgaas [this message]
2021-08-30 20:21 ` Sergio Miguéns Iglesias
2021-09-01 8:41 ` Juergen Gross
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=20210830191810.GA13209@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lonyelon@gmail.com \
--cc=sergio@lony.xyz \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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®