linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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, 4 Jul 2021 18:34:25 +0100	[thread overview]
Message-ID: <20210704183425.34df79ef@jic23-huawei> (raw)
In-Reply-To: <20210618123005.49867-1-paul@crapouillou.net>

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.

Thanks,

Jonathan

> 
> Cheers,
> -Paul
> 
> Paul Cercueil (2):
>   iio: core: Forbid use of both labels and extended names
>   iio: core: Support reading extended name as label
> 
>  drivers/iio/industrialio-core.c | 33 +++++++++++++++++++++++++++++----
>  1 file changed, 29 insertions(+), 4 deletions(-)
> 


  parent reply	other threads:[~2021-07-04 17:32 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 ` Jonathan Cameron [this message]
2021-07-04 21:18   ` [PATCH v3 0/2] Add "extended_name" to label Paul Cercueil
2021-07-18 14:42     ` Jonathan Cameron

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=20210704183425.34df79ef@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).