From: Jonathan Cameron <jic23@kernel.org>
To: Michal Simek <michal.simek@xilinx.com>
Cc: Robert Hancock <robert.hancock@calian.com>,
"anand.ashok.dumbre@xilinx.com" <anand.ashok.dumbre@xilinx.com>,
"lars@metafoo.de" <lars@metafoo.de>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"manish.narani@xilinx.com" <manish.narani@xilinx.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] Xilinx AMS fixes
Date: Mon, 28 Feb 2022 18:26:26 +0000 [thread overview]
Message-ID: <20220228182626.12544642@jic23-huawei> (raw)
In-Reply-To: <56c261b2-2bf0-16d1-8fdb-a264709cba09@xilinx.com>
On Mon, 28 Feb 2022 07:40:59 +0100
Michal Simek <michal.simek@xilinx.com> wrote:
> On 2/26/22 17:45, Jonathan Cameron wrote:
> > On Wed, 9 Feb 2022 19:49:27 +0000
> > Robert Hancock <robert.hancock@calian.com> wrote:
> >
> >> On Sun, 2022-01-30 at 12:46 +0000, Jonathan Cameron wrote:
> >>> On Thu, 27 Jan 2022 11:34:46 -0600
> >>> Robert Hancock <robert.hancock@calian.com> wrote:
> >>>
> >>>> Various fixes for the Xilinx AMS driver.
> >>>>
> >>>> Changes since v1:
> >>>> -drop addition to ZynqMP device tree, will be submitted elsewhere
> >>>> -add patch to fix DT binding to add missing clock entry
> >>>
> >>> I'm fine with these but would like to leave them all on list a tiny
> >>> bit longer so we can hopefully get some review, particularly on patches
> >>> 1 and 4.
> >>>
> >>> Jonathan
> >>
> >> Hi all,
> >>
> >> I don't think I've gotten any feedback. Is anyone able to review/test?
> >>
> > Michal,
> >
> > If you have a chance to take a quick look at this series that would
> > be great.
>
> That series looks good to me. Please apply and feel free to add my
>
> Acked-by: Michal Simek <michal.simek@xilinx.com>
>
Applied to the fixes-togreg branch of iio.git.
I'm not certain I'll get a fixes pull request out in time to make this
cycle so these might get dragged across to my togreg branch and
added to a pull request for the merge window. Or, possibly Greg
will take them for the merge window even if I do a separate pull given
we are close to the end of the cycle.
Thanks,
Jonathan
> Thanks,
> Michal
next prev parent reply other threads:[~2022-02-28 18:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 17:34 [PATCH v2 0/4] Xilinx AMS fixes Robert Hancock
2022-01-27 17:34 ` [PATCH v2 1/4] dt-bindings: iio: adc: zynqmp_ams: Add clock entry Robert Hancock
2022-02-09 20:12 ` Rob Herring
2022-01-27 17:34 ` [PATCH v2 2/4] iio: adc: xilinx-ams: Fixed missing PS channels Robert Hancock
2022-01-27 17:34 ` [PATCH v2 3/4] iio: adc: xilinx-ams: Fixed wrong sequencer register settings Robert Hancock
2022-01-27 17:34 ` [PATCH v2 4/4] iio: adc: xilinx-ams: Fix single channel switching sequence Robert Hancock
2022-01-30 12:46 ` [PATCH v2 0/4] Xilinx AMS fixes Jonathan Cameron
2022-02-09 19:49 ` Robert Hancock
2022-02-26 16:45 ` Jonathan Cameron
2022-02-28 6:40 ` Michal Simek
2022-02-28 18:26 ` Jonathan Cameron [this message]
2022-03-01 7:34 ` Michal Simek
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=20220228182626.12544642@jic23-huawei \
--to=jic23@kernel.org \
--cc=anand.ashok.dumbre@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=manish.narani@xilinx.com \
--cc=michal.simek@xilinx.com \
--cc=robert.hancock@calian.com \
--cc=robh+dt@kernel.org \
/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).