From: P J P <ppandit@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Alistair Francis <alistair23@gmail.com>,
Qemu Developers <qemu-devel@nongnu.org>,
Wjjzhang <wjjzhang@tencent.com>, Jiang Xin <jiangxin1@huawei.com>
Subject: Re: [Qemu-devel] [PATCH v4 2/4] sd: sdhci: check transfer mode register in multi block transfer
Date: Mon, 20 Feb 2017 13:14:21 +0530 (IST) [thread overview]
Message-ID: <alpine.LFD.2.20.1702201313310.21397@wniryva> (raw)
In-Reply-To: <CAFEAcA9B4s0_7yBCG3Jraym_NABWZhk6JQ10sb95waQgN-YCuA@mail.gmail.com>
+-- On Fri, 17 Feb 2017, Peter Maydell wrote --+
| Alistair's point is that when you resend a patchset where some patches have
| got reviews/acks and those patches haven't changed significantly, you should
| include the Reviewed-by: or Acked-by: tags in the commit messages on the
| resent patches, so that people know they don't need to reexamine those
| patches.
Ah okay, noted; Will do.
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
next prev parent reply other threads:[~2017-02-20 7:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 18:52 [Qemu-devel] [PATCH v4 0/4] sd: sdhci: correct transfer mode register usage P J P
2017-02-14 18:52 ` [Qemu-devel] [PATCH v4 1/4] sd: sdhci: mask transfer mode register value P J P
2017-02-14 19:12 ` Alistair Francis
2017-02-14 18:52 ` [Qemu-devel] [PATCH v4 2/4] sd: sdhci: check transfer mode register in multi block transfer P J P
2017-02-14 19:13 ` Alistair Francis
2017-02-15 4:58 ` P J P
2017-02-17 13:10 ` Peter Maydell
2017-02-20 7:44 ` P J P [this message]
2017-02-14 18:52 ` [Qemu-devel] [PATCH v4 3/4] sd: sdhci: conditionally invoke " P J P
2017-02-14 18:52 ` [Qemu-devel] [PATCH v4 4/4] sd: sdhci: Remove block count enable check in single block transfers P J P
2017-02-17 21:54 ` Alistair Francis
2017-02-17 13:21 ` [Qemu-devel] [PATCH v4 0/4] sd: sdhci: correct transfer mode register usage Peter Maydell
2017-02-17 21:55 ` Alistair Francis
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=alpine.LFD.2.20.1702201313310.21397@wniryva \
--to=ppandit@redhat.com \
--cc=alistair23@gmail.com \
--cc=jiangxin1@huawei.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=wjjzhang@tencent.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).