From: Jonathan Corbet <corbet@lwn.net>
To: Jonathan Cameron <jic23@kernel.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
linux-kernel@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 0/2] doc: add a couple fixups for IIO ABI files
Date: Thu, 27 May 2021 10:09:14 -0600 [thread overview]
Message-ID: <87zgwg2m6t.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210526175908.42db03a0@jic23-huawei>
Jonathan Cameron <jic23@kernel.org> writes:
> On Tue, 25 May 2021 14:23:51 +0200
> Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
>
>> Patch 1 was already submitted as patch 10/10 on this series:
>> https://lore.kernel.org/linux-doc/87wnrtnpko.fsf@meer.lwn.net/
>>
>> However, it generated a new warning, due to a separate issue.
>>
>> So, resend it together with a warning fix patch.
>>
>> As these patches are independent from the other ones, I guess it
>> can either be applied via IIO or via docs tree, whatever works
>> best for the doc and IIO maintainers.
>> So, I should leave such decision to Jonathan & Jonathan ;-)
>
> Either works for me, but on basis I got here first.
>
> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> Jon, if you'd prefer I picked these up, then let me know.
I've applied them, thanks; I took the liberty of fixing the spelling of
"specify" in the second one :)
jon
prev parent reply other threads:[~2021-05-27 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 12:23 Mauro Carvalho Chehab
2021-05-25 12:23 ` [PATCH 1/2] iio: ABI: sysfs-bus-iio: fix a typo Mauro Carvalho Chehab
2021-05-25 12:23 ` [PATCH 2/2] iio: ABI: sysfs-bus-iio: avoid a warning when doc is built Mauro Carvalho Chehab
2021-05-26 16:59 ` [PATCH 0/2] doc: add a couple fixups for IIO ABI files Jonathan Cameron
2021-05-27 16:09 ` Jonathan Corbet [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=87zgwg2m6t.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@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
all inboxes | Powered by JetHome®