From: Lee Jones <lee.jones@linaro.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: linux-kernel@vger.kernel.org, Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
linux-iio@vger.kernel.org,
Ryan Barnett <ryan.barnett@collins.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH v5] mfd: ti_am335x_tscadc: Add ADC1/magnetic reader support
Date: Tue, 12 Oct 2021 11:56:46 +0100 [thread overview]
Message-ID: <YWVp7pftLsmm40zZ@google.com> (raw)
In-Reply-To: <20211004155319.1507652-1-miquel.raynal@bootlin.com>
On Mon, 04 Oct 2021, Miquel Raynal wrote:
> Introduce a new compatible that has another set of driver data,
> targeting am437x SoCs with a magnetic reader instead of the
> touchscreen and a more featureful set of registers.
>
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
>
> Changes in v5:
> * Let the 48 v4 patch series aside, while only resending this patch that
> triggered a robot warning. Use the use_mag boolean instead of sticking
> to tscmag_wires which was not optimal anyway, silencing the 'not used'
> warning while keeping the code simple and clear.
>
>
> drivers/mfd/ti_am335x_tscadc.c | 37 ++++++++++++++++++++++------
> include/linux/mfd/ti_am335x_tscadc.h | 6 +++++
> 2 files changed, 36 insertions(+), 7 deletions(-)
Okay, so I've been battling with this set for a while. I've finally
managed to figure out how to apply the whole set including this
straggler, but Patch 10 is not applying to my tree. Could you please
rebase and resend the whole set with this one included please?
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2021-10-12 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 15:53 [PATCH v5] mfd: ti_am335x_tscadc: Add ADC1/magnetic reader support Miquel Raynal
2021-10-12 10:56 ` Lee Jones [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=YWVp7pftLsmm40zZ@google.com \
--to=lee.jones@linaro.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=ryan.barnett@collins.com \
--cc=thomas.petazzoni@bootlin.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