linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: Peter Rosin <peda@axentia.se>, <linux-kernel@vger.kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Sean Nyekjaer <sean@geanix.com>, <linux-iio@vger.kernel.org>,
	<devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] Add support for texas dac121c081 to the dac5571 driver
Date: Sun, 22 May 2022 12:57:55 +0100	[thread overview]
Message-ID: <20220522125755.099b5452@jic23-huawei> (raw)
In-Reply-To: <20220512140232.000078c1@Huawei.com>

On Thu, 12 May 2022 14:02:32 +0100
Jonathan Cameron <Jonathan.Cameron@Huawei.com> wrote:

> On Thu, 12 May 2022 10:59:48 +0200
> Peter Rosin <peda@axentia.se> wrote:
> 
> > HI!
> > 
> > 2022-05-01 at 20:03, Jonathan Cameron wrote:  
> > > On Thu, 28 Apr 2022 20:44:39 +0100
> > > Jonathan Cameron <jic23@kernel.org> wrote:
> > >     
> > >> On Mon, 25 Apr 2022 22:46:30 +0200
> > >> Peter Rosin <peda@axentia.se> wrote:
> > >>    
> > >>> Hi!
> > >>>
> > >>> The new chip works much like the other chips supported by the driver, so
> > >>> this is just adding another compatible to the list.
> > >>>
> > >>> Chenages since v1:
> > >>> - Guenter Roeck noticed elsewhere that my mail setup was botched and
> > >>>   that my patches were clobbered. Hopefully fixed. *blush*
> > >>> - added tags from Sean Nyekjaer and Rob Herring      
> > >>
> > >> Applied.  Thanks    
> > > 
> > > Backed out temporarily because they have crossed with a fix (that I'd
> > > forgotten about) and were requiring a non trivial merge in linux-next.
> > > 
> > > https://patchwork.kernel.org/project/linux-iio/patch/20220324234340.32402-1-laurent.pinchart@ideasonboard.com/
> > > 
> > > Hopefully that will get resolved in my upstream fairly soon and I can
> > > fix this one up whilst applying it myself.    
> > 
> > Looks like it might be time to bring this one in from the cold?  
> 
> Nearly.  I have a pull request out to Greg. Once he's taken that
> I'll fastforward the togreg branch to include the fix and
> can then apply this.

Now we are good. Applied to the togreg branch of iio.git and added the
tweak needed to provide data in the of_device_id table.

Unfortunately timing is against me this time, and unless the merge window
is delayed this is now 5.20 material.

Thanks,

Jonathan

> 
> Jonathan
> 
> > 
> > Cheers,
> > Peter  
> 


      reply	other threads:[~2022-05-22 11:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 20:46 [PATCH v2 0/2] Add support for texas dac121c081 to the dac5571 driver Peter Rosin
2022-04-25 20:46 ` [PATCH v2 1/2] dt-bindings: iio: ti-dac5571: Add ti,dac121c081 Peter Rosin
2022-04-25 20:47 ` [PATCH v2 2/2] iio: dac: ti-dac5571: add support for ti,dac121c081 Peter Rosin
2022-04-28 19:44 ` [PATCH v2 0/2] Add support for texas dac121c081 to the dac5571 driver Jonathan Cameron
2022-05-01 18:03   ` Jonathan Cameron
2022-05-12  8:59     ` Peter Rosin
2022-05-12 13:02       ` Jonathan Cameron
2022-05-22 11:57         ` 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=20220522125755.099b5452@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Jonathan.Cameron@Huawei.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peda@axentia.se \
    --cc=robh+dt@kernel.org \
    --cc=sean@geanix.com \
    /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).