Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Date:   Thu, 12 May 2022 14:02:32 +0100
From:   Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To:     Peter Rosin <peda@axentia.se>
CC:     Jonathan Cameron <jic23@kernel.org>,
        <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
Message-ID: <20220512140232.000078c1@Huawei.com>
In-Reply-To: <06546c40-639a-01e4-ed99-4895edfe8211@axentia.se>
References: <42db911c-5eba-0511-3e8c-8011a2a5b44a@axentia.se>
        <20220428204439.4ec2b4ae@jic23-huawei>
        <20220501190349.54aa48a3@jic23-huawei>
        <06546c40-639a-01e4-ed99-4895edfe8211@axentia.se>
Organization: Huawei Technologies Research and Development (UK) Ltd.
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Precedence: bulk

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.

Jonathan

> 
> Cheers,
> Peter