From: Jonathan Cameron <jic23@kernel.org>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: heiko@sntech.de, linux-rockchip@lists.infradead.org,
Simon Xue <xxm@rock-chips.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] iio: adc: rockchip_saradc: add rk3562
Date: Tue, 4 Mar 2025 15:04:08 +0000 [thread overview]
Message-ID: <20250304150408.60864bbd@jic23-huawei> (raw)
In-Reply-To: <20250227110343.2342017-2-kever.yang@rock-chips.com>
On Thu, 27 Feb 2025 19:03:43 +0800
Kever Yang <kever.yang@rock-chips.com> wrote:
> From: Simon Xue <xxm@rock-chips.com>
>
> rk3562 is using v2 saradc with 8 channels.
>
> Signed-off-by: Simon Xue <xxm@rock-chips.com>
> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> ---
>
> Changes in v2: None
>
> drivers/iio/adc/rockchip_saradc.c | 24 +++++++++++++++++++++++-
> 1 file changed, 23 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iio/adc/rockchip_saradc.c b/drivers/iio/adc/rockchip_saradc.c
> index a29e54754c8f..9995f95bafe0 100644
> --- a/drivers/iio/adc/rockchip_saradc.c
> +++ b/drivers/iio/adc/rockchip_saradc.c
> @@ -1,7 +1,7 @@
> // SPDX-License-Identifier: GPL-2.0-or-later
> /*
> * Rockchip Successive Approximation Register (SAR) A/D Converter
> - * Copyright (C) 2014 ROCKCHIP, Inc.
> + * Copyright (C) 2014 Rockchip Electronics Co., Ltd.
This 'fixup' should have been mentioned in the patch description.
Not that important though so I'll leave it this time.
next prev parent reply other threads:[~2025-03-04 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 11:03 [PATCH v2 1/2] dt-bindings: iio: adc: Add rockchip,rk3562-saradc string Kever Yang
2025-02-27 11:03 ` [PATCH v2 2/2] iio: adc: rockchip_saradc: add rk3562 Kever Yang
2025-03-04 15:04 ` Jonathan Cameron [this message]
2025-02-28 20:06 ` [PATCH v2 1/2] dt-bindings: iio: adc: Add rockchip,rk3562-saradc string Rob Herring (Arm)
2025-03-04 15:01 ` Jonathan Cameron
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=20250304150408.60864bbd@jic23-huawei \
--to=jic23@kernel.org \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=xxm@rock-chips.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