From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
linux-iio@vger.kernel.org,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: iio: adc: add ad7944 ADCs
Date: Thu, 29 Feb 2024 13:27:26 -0500 [thread overview]
Message-ID: <20240229-imaginary-sophisticated-dodo-5b97b8@lemur> (raw)
In-Reply-To: <CAMknhBHhrNc-6qggSD1pt8djc9cv93dyNON8c_np6RwqT3yzig@mail.gmail.com>
On Thu, Feb 29, 2024 at 08:35:47AM -0600, David Lechner wrote:
> Oh geez, yeah really dumb mistake. Will resend. I do use b4 but it
> doesn't handle per-patch changelogs that I know of.
b4 directly doesn't, but you can put them under --- in individual commits and
they should be preserved and included on send. E.g.:
foodrv: add new device bar-0x555
The commit message that should go into the tree.
Signed-off-by: You <you@example.com>
---
Changes:
v3: add foo to bar
-K
next prev parent reply other threads:[~2024-02-29 18:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 18:10 [PATCH v3 0/2] iio: adc: ad7944: new driver David Lechner
2024-02-28 18:10 ` [PATCH v3 1/2] dt-bindings: iio: adc: add ad7944 ADCs David Lechner
2024-02-29 9:40 ` Krzysztof Kozlowski
2024-02-29 14:35 ` David Lechner
2024-02-29 15:29 ` Krzysztof Kozlowski
2024-02-29 18:27 ` Konstantin Ryabitsev [this message]
2024-02-28 18:10 ` [PATCH v3 2/2] iio: adc: ad7944: add driver for AD7944/AD7985/AD7986 David Lechner
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=20240229-imaginary-sophisticated-dodo-5b97b8@lemur \
--to=konstantin@linuxfoundation.org \
--cc=Michael.Hennerich@analog.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh+dt@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