From: Chris Ruehl <chris.ruehl@gtsys.com.hk>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org,
"Michael Hennerich" <michael.hennerich@analog.com>,
"Jonathan Cameron" <jic23@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>,
"Alexios Zavras" <alexios.zavras@intel.com>,
"Steve Winslow" <swinslow@gmail.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/3] iio/dac: convert ltc2632.txt to lltc,ltc2632.yaml
Date: Mon, 10 Aug 2020 11:01:25 +0800 [thread overview]
Message-ID: <95f3873d-c101-7a64-8456-840378dd49f3@gtsys.com.hk> (raw)
In-Reply-To: <20200430152414.GA19887@bogus>
Rob,
On 30/4/2020 11:24 pm, Rob Herring wrote:
> On Mon, Apr 20, 2020 at 12:26:08PM +0800, Chris Ruehl wrote:
>> Conversion of the ltc2632 to yaml format and name the file 'lltc,ltc2632.yaml'.
>>
>> Signed-off-by: Chris Ruehl <chris.ruehl@gtsys.com.hk>
>> ---
>> v5:
>> correct require section
>> set maintainer of analog.com
>> v4..v2: no change
1/3 and 2/3 make it already to linux-next.
I will send 3/3 with the corrections you requested as a new
stand alone patch and refer commit 6f1c9e0da9aae51177457731357ae8a2c8af27cd
for reference.
Regards
Chris
prev parent reply other threads:[~2020-08-10 3:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 4:26 [PATCH v5] iio: patch set ltc2632 Chris Ruehl
2020-04-20 4:26 ` [PATCH v5 1/3] iio: documentation ltc2632_chip_info add num_channels Chris Ruehl
2020-04-25 19:37 ` Jonathan Cameron
2020-04-20 4:26 ` [PATCH v5 2/3] iio: DAC extension for ltc2634-12/10/8 Chris Ruehl
2020-04-30 15:17 ` Rob Herring
2020-04-20 4:26 ` [PATCH v5 3/3] iio/dac: convert ltc2632.txt to lltc,ltc2632.yaml Chris Ruehl
2020-04-25 19:35 ` Jonathan Cameron
2020-04-27 1:09 ` Chris Ruehl
2020-04-30 15:24 ` Rob Herring
2020-08-10 3:01 ` Chris Ruehl [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=95f3873d-c101-7a64-8456-840378dd49f3@gtsys.com.hk \
--to=chris.ruehl@gtsys.com.hk \
--cc=alexios.zavras@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=pmeerw@pmeerw.net \
--cc=robh@kernel.org \
--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).