All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	linux-iio@vger.kernel.org,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Prabhakar Mahadev Lad" <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	linux-renesas-soc@vger.kernel.org,
	"Sean Nyekjaer" <sean@geanix.com>
Subject: Re: [PATCH v2 0/2] Match data improvements for ti-dac5571 driver
Date: Mon, 28 Aug 2023 13:50:40 +0100	[thread overview]
Message-ID: <20230828135040.37e1aeb7@jic23-huawei> (raw)
In-Reply-To: <20230818173907.323640-1-biju.das.jz@bp.renesas.com>

On Fri, 18 Aug 2023 18:39:05 +0100
Biju Das <biju.das.jz@bp.renesas.com> wrote:

> This patch series aims to add match data improvements for ti-dac5571
> driver.
> 
> v1->v2:
>  * Split the patch into two.
>  * Added patch#2 for sorting match tables.
> 
> Biju Das (2):
>   iio: dac: ti-dac5571: Use i2c_get_match_data()
>   iio: dac: ti-dac5571: Sort match tables
+CC Sean,

Applied to the togreg branch of iio.git and pushed out for now as testing.
I'll be rebasing that tree on rc1 once available, so I won't push these
out in a form linux-next will pick up until then.

Thanks,

Jonathan

> 
>  drivers/iio/dac/ti-dac5571.c | 48 ++++++++++++++++--------------------
>  1 file changed, 21 insertions(+), 27 deletions(-)
> 


      parent reply	other threads:[~2023-08-28 12:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18 17:39 [PATCH v2 0/2] Match data improvements for ti-dac5571 driver Biju Das
2023-08-18 17:39 ` [PATCH v2 1/2] iio: dac: ti-dac5571: Use i2c_get_match_data() Biju Das
2023-08-28 13:44   ` Laurent Pinchart
2023-08-29 14:42     ` Biju Das
2023-08-18 17:39 ` [PATCH v2 2/2] iio: dac: ti-dac5571: Sort match tables Biju Das
2023-08-28 13:50   ` Laurent Pinchart
2023-08-28 12:50 ` 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=20230828135040.37e1aeb7@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=geert+renesas@glider.be \
    --cc=lars@metafoo.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=sean@geanix.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.