From: Bjorn Helgaas <helgaas@kernel.org>
To: Vaibhav Gupta <vaibhavgupta40@gmail.com>
Cc: Damien Le Moal <Damien.LeMoal@wdc.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Bjorn Helgaas <bjorn@helgaas.com>,
Vaibhav Gupta <vaibhav.varodek@gmail.com>,
Jens Axboe <axboe@kernel.dk>,
Joshua Morris <josh.h.morris@us.ibm.com>,
Philip Kelleher <pjk1939@linux.ibm.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-kernel-mentees@lists.linuxfoundation.org"
<linux-kernel-mentees@lists.linuxfoundation.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2 3/3] skd: use generic power management
Date: Wed, 22 Jul 2020 12:52:47 -0500 [thread overview]
Message-ID: <20200722175247.GA1293794@bjorn-Precision-5520> (raw)
In-Reply-To: <20200721070939.GB51743@gmail.com>
On Tue, Jul 21, 2020 at 12:39:39PM +0530, Vaibhav Gupta wrote:
> Okay. I will improve on it. Just inform me after testing that if any other
> changes are required. I guess [PATCH 1/3] and [PATCH 2/3] are okay, so I will
> only send v3 of [PATCH 3/3] after suggested changes.
FWIW, there's a recent conversation on users@linux.kernel.org about
updating individual patches in a series (sorry, can't find a link to
it). But the gist of it was that posting only [v3 3/3] leads to
confusion because
- we can't tell whether [v3 1/3] and [v3 2/3] got lost en-route, and
- collecting things from v2 and v3 is more work for the maintainer.
Bottom line: repost the whole series, even if some patches haven't
changed.
Bjorn
next prev parent reply other threads:[~2020-07-22 17:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 8:09 [PATCH v1 0/3] block: use generic power management Vaibhav Gupta
2020-07-17 8:09 ` [PATCH v1 1/3] mtip32xx: " Vaibhav Gupta
2020-07-17 8:09 ` [PATCH v1 2/3] rsxx: " Vaibhav Gupta
2020-07-17 8:09 ` [PATCH v1 3/3] skd: " Vaibhav Gupta
2020-07-20 12:52 ` Damien Le Moal
2020-07-20 13:16 ` Vaibhav Gupta
2020-07-21 2:49 ` Damien Le Moal
2020-07-21 7:04 ` Vaibhav Gupta
2020-07-20 13:29 ` [PATCH v2 0/3] block: " Vaibhav Gupta
2020-07-20 13:30 ` [PATCH v2 1/3] mtip32xx: " Vaibhav Gupta
2020-07-20 13:30 ` [PATCH v2 2/3] rsxx: " Vaibhav Gupta
2020-07-20 13:30 ` [PATCH v2 3/3] skd: " Vaibhav Gupta
2020-07-21 2:57 ` Damien Le Moal
2020-07-21 7:09 ` Vaibhav Gupta
2020-07-22 6:28 ` Damien Le Moal
2020-07-22 7:21 ` Vaibhav Gupta
2020-07-22 8:33 ` [PATCH v3 0/3] block: " Vaibhav Gupta
2020-07-22 8:33 ` [PATCH v3 1/3] mtip32xx: " Vaibhav Gupta
2020-07-22 8:33 ` [PATCH v3 2/3] rsxx: " Vaibhav Gupta
2020-07-22 8:33 ` [PATCH v3 3/3] skd: " Vaibhav Gupta
2020-07-27 2:14 ` Damien Le Moal
2020-08-17 7:55 ` [PATCH v3 0/3] block: " Vaibhav Gupta
2021-01-14 11:54 ` [PATCH v4 " Vaibhav Gupta
2021-01-14 11:54 ` [PATCH v4 1/3] mtip32xx: " Vaibhav Gupta
2021-01-14 11:54 ` [PATCH v4 2/3] rsxx: " Vaibhav Gupta
2021-01-14 11:54 ` [PATCH v4 3/3] skd: " Vaibhav Gupta
2020-07-22 17:52 ` Bjorn Helgaas [this message]
2020-07-22 18:07 ` [PATCH v2 " Vaibhav Gupta
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=20200722175247.GA1293794@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=Damien.LeMoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=bhelgaas@google.com \
--cc=bjorn@helgaas.com \
--cc=josh.h.morris@us.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pjk1939@linux.ibm.com \
--cc=skhan@linuxfoundation.org \
--cc=vaibhav.varodek@gmail.com \
--cc=vaibhavgupta40@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).