From: Jonathan Cameron <jic23@kernel.org>
To: Paul Cercueil <paul@crapouillou.net>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Alexandru Ardelean <ardeleanalex@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Add "extended_name" to label
Date: Sun, 18 Jul 2021 15:42:59 +0100 [thread overview]
Message-ID: <20210718154259.1aaf69a2@jic23-huawei> (raw)
In-Reply-To: <AIOQVQ.VCBVMZQG56T83@crapouillou.net>
On Sun, 04 Jul 2021 22:18:10 +0100
Paul Cercueil <paul@crapouillou.net> wrote:
> Hi Jonathan,
>
> Le dim., juil. 4 2021 at 18:34:25 +0100, Jonathan Cameron
> <jic23@kernel.org> a écrit :
> > On Fri, 18 Jun 2021 13:30:03 +0100
> > Paul Cercueil <paul@crapouillou.net> wrote:
> >
> >> Hi Jonathan,
> >>
> >> This is the v3 of my patchset that sets the label attribute to the
> >> "extended_name".
> >>
> >> v3 only refactors the code of patch [2/2] to make it look a bit
> >> better.
> >
> > Hi Paul,
> >
> > Just thought I'd let you know v3 looks great to me. Timing meant I
> > didn't
> > manage to get it into last cycle, and am now waiting for rc1 to give
> > a nice
> > place to rebase my trees on. Hence I'll pick this up in a week or
> > two.
>
> That's perfectly fine, I wasn't expecting it to land before rc1.
Applied to the togreg branch of iio.git and pushed out as testing for 0-day
to poke at it before I push it out in a fashion that makes tidying
any issues up messy.
Thanks,
Jonathan
>
> Cheers,
> -Paul
>
>
prev parent reply other threads:[~2021-07-18 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 12:30 [PATCH v3 0/2] Add "extended_name" to label Paul Cercueil
2021-06-18 12:30 ` [PATCH v3 1/2] iio: core: Forbid use of both labels and extended names Paul Cercueil
2021-06-18 12:30 ` [PATCH v3 2/2] iio: core: Support reading extended name as label Paul Cercueil
2021-07-04 17:34 ` [PATCH v3 0/2] Add "extended_name" to label Jonathan Cameron
2021-07-04 21:18 ` Paul Cercueil
2021-07-18 14:42 ` 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=20210718154259.1aaf69a2@jic23-huawei \
--to=jic23@kernel.org \
--cc=ardeleanalex@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@crapouillou.net \
/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).