From: Mark Brown <broonie@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
linux-iio@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-ide@vger.kernel.org, linux-clk@vger.kernel.org,
drbd-dev@lists.linbit.com,
"Neil Armstrong" <narmstrong@baylibre.com>,
linux-stm32@st-md-mailman.stormreply.com,
linux-acpi@vger.kernel.org,
"Jerome Brunet" <jbrunet@baylibre.com>,
"David Lechner" <david@lechnology.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
linux-block@vger.kernel.org, linux-amlogic@lists.infradead.org,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org,
"Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
"Julia Lawall" <Julia.Lawall@inria.fr>,
linux-crypto@vger.kernel.org,
openipmi-developer@lists.sourceforge.net
Subject: Re: [PATCH 00/18] use semicolons rather than commas to separate statements
Date: Tue, 29 Sep 2020 12:37:45 +0100 [thread overview]
Message-ID: <20200929113745.GB4799@sirena.org.uk> (raw)
In-Reply-To: <b1174f9be2ce65f6b5ebefcba0b48e792926abbc.camel@perches.com>
[-- Attachment #1.1: Type: text/plain, Size: 676 bytes --]
On Mon, Sep 28, 2020 at 05:45:24PM -0700, Joe Perches wrote:
> On Mon, 2020-09-28 at 20:35 +0100, Mark Brown wrote:
> > [1/1] regmap: debugfs: use semicolons rather than commas to separate statements
> > commit: 7f4a122d0b50b40c64d24a5cf7aafe26dd9487ee
> Rather than replying to the 0/n cover letter to a patch
> series, can you reply to each of the specific patches in
> the patch series you are applying?
> Otherwise, it's a bit difficult to figure out which patches
> you are applying.
Feel free to submit patches to b4. Ideally things like this wouldn't be
being sent as serieses in the first place, there's no dependencies or
interactions between the patches.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2020-09-29 11:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 19:12 Julia Lawall
2020-09-27 19:12 ` [PATCH 10/18] clk: meson: " Julia Lawall
2020-09-28 9:47 ` Jerome Brunet
2020-10-08 1:54 ` Stephen Boyd
2020-10-14 0:44 ` Stephen Boyd
2020-09-27 20:08 ` [PATCH 00/18] " Joe Perches
2020-09-28 19:35 ` Mark Brown
2020-09-29 0:45 ` Joe Perches
2020-09-29 11:37 ` Mark Brown [this message]
2020-09-29 11:46 ` Julia Lawall
2020-09-29 12:37 ` Mark Brown
2020-09-29 12:44 ` Julia Lawall
2020-09-30 19:33 ` Joe Perches
2020-10-01 11:01 ` Mark Brown
2020-10-03 18:40 ` Joe Perches
2020-10-03 19:15 ` Konstantin Ryabitsev
2020-10-03 19:18 ` Julia Lawall
2020-10-03 19:31 ` Konstantin Ryabitsev
2020-10-03 19:43 ` Joe Perches
2020-10-05 16:52 ` Mark Brown
2020-10-03 19:27 ` Joe Perches
2020-10-03 19:36 ` Joe Perches
2020-09-29 12:20 ` Ard Biesheuvel
2020-09-29 12:36 ` Julia Lawall
2020-09-29 12:41 ` Dan Carpenter
2020-09-29 12:47 ` Julia Lawall
2020-09-29 13:34 ` Joe Perches
2020-09-29 13:42 ` Julia Lawall
2020-09-29 13:42 ` Shuah Khan
2020-10-02 16:47 ` Shuah Khan
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=20200929113745.GB4799@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Julia.Lawall@inria.fr \
--cc=david@lechnology.com \
--cc=drbd-dev@lists.linbit.com \
--cc=jbrunet@baylibre.com \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
--cc=valdis.kletnieks@vt.edu \
/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®