From: Jonathan Cameron <jic23@kernel.org>
To: Ramona Alexandra Nechita <ramona.nechita@analog.com>
Cc: <linux-iio@vger.kernel.org>, Lars-Peter Clausen <lars@metafoo.de>,
Cosmin Tanislav <cosmin.tanislav@analog.com>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Nuno Sa <nuno.sa@analog.com>,
Marius Cristea <marius.cristea@microchip.com>,
Marcelo Schmitt <marcelo.schmitt@analog.com>,
Maksim Kiselev <bigunclemax@gmail.com>,
Liam Beguin <liambeguin@gmail.com>,
Ivan Mikhaylov <fr0st61te@gmail.com>,
Marcus Folkesson <marcus.folkesson@gmail.com>,
Lee Jones <lee@kernel.org>,
Mike Looijmans <mike.looijmans@topic.nl>,
Okan Sahin <okan.sahin@analog.com>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 0/3] ad777x driver addressing patch comments
Date: Sun, 23 Jun 2024 13:43:21 +0100 [thread overview]
Message-ID: <20240623134321.6c8ad61f@jic23-huawei> (raw)
In-Reply-To: <20240619122105.22642-1-ramona.nechita@analog.com>
Don't change the patch title of a series mid way through multiple revisions
without a very good reason. Some of the automation we use relies on those
matching to ensure the latest version is picked up.
J
next prev parent reply other threads:[~2024-06-23 12:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 12:20 [PATCH v3 0/3] ad777x driver addressing patch comments Ramona Alexandra Nechita
2024-06-19 12:20 ` [PATCH v3 1/3] dt-bindings: iio: adc: add a7779 doc Ramona Alexandra Nechita
2024-06-19 13:20 ` Rob Herring (Arm)
2024-06-19 17:42 ` Conor Dooley
2024-06-23 12:41 ` Jonathan Cameron
2024-06-23 12:43 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-19 12:22 [PATCH v3 0/3] ad777x driver addressing patch comments Ramona Alexandra Nechita
2024-06-19 12:24 Ramona Alexandra Nechita
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=20240623134321.6c8ad61f@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bigunclemax@gmail.com \
--cc=conor+dt@kernel.org \
--cc=cosmin.tanislav@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=fr0st61te@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=lee@kernel.org \
--cc=liambeguin@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt@analog.com \
--cc=marcus.folkesson@gmail.com \
--cc=marius.cristea@microchip.com \
--cc=mike.looijmans@topic.nl \
--cc=nuno.sa@analog.com \
--cc=okan.sahin@analog.com \
--cc=ramona.nechita@analog.com \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).