From: Jonathan Cameron <jic23@kernel.org>
To: Chris Ruehl <chris.ruehl@gtsys.com.hk>
Cc: devicetree@vger.kernel.org, "Hartmut Knaack" <knaack.h@gmx.de>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Peter Meerwald-Stadler" <pmeerw@pmeerw.net>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Steve Winslow" <swinslow@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: patch set ltc2632
Date: Tue, 14 Apr 2020 19:01:22 +0100 [thread overview]
Message-ID: <20200414190122.6881a478@archlinux> (raw)
In-Reply-To: <20200414062648.19013-1-chris.ruehl@gtsys.com.hk>
On Tue, 14 Apr 2020 14:26:43 +0800
Chris Ruehl <chris.ruehl@gtsys.com.hk> wrote:
> Patchset to extend ltc2632 spi driver to support the similar chip set
> ltc2634.
> * Patch v2 1/3 update documentation struct ltc2632_chip_info
> * Patch v2 2/3 patch ltc2632.c,Kconfig,ltc2632.txt(devtree)
> * Patch v2 3/3 convert ltc2632.txt to yaml format named lltc,ltc2632.yaml
Hi Chris,
Still something going on with your git send-email. Are you sending these one
by one perhaps? Or maybe have something odd in your .git/config?
These have turned up as a series of independent messages as the in-reply-to
field isn't set in the patches (which should point to this one).
git-send-email will do that automatically by default if pointed at all the
files in one go.
Thanks,
Jonathan
>
> Signed-off-by: Chris Ruehl <chris.ruehl@gtsys.com.hk>
> ---
>
prev parent reply other threads:[~2020-04-14 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 6:26 [PATCH v2] iio: patch set ltc2632 Chris Ruehl
2020-04-14 18:01 ` Jonathan Cameron [this message]
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=20200414190122.6881a478@archlinux \
--to=jic23@kernel.org \
--cc=chris.ruehl@gtsys.com.hk \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=swinslow@gmail.com \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
/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).