From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Wolfram Sang <wsa@kernel.org>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Gross <agross@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: remove duplicate entry for i2c-qcom-geni
Date: Fri, 18 Feb 2022 09:52:59 -0800 [thread overview]
Message-ID: <Yg/c+27yR1P0b+eL@ripper> (raw)
In-Reply-To: <20220218104904.14405-1-wsa@kernel.org>
On Fri 18 Feb 02:49 PST 2022, Wolfram Sang wrote:
> The driver is already covered in the ARM/QUALCOMM section. Also, Akash
> Asthana's email bounces meanwhile and Mukesh Savaliya has never
> responded to mails regarding this driver.
>
> Signed-off-by: Wolfram Sang <wsa@kernel.org>
It would have been nice to go the other direction (reducing
ARM/QUALCOMM), but your assessment looks accurate, so:
Acked-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Regards,
Bjorn
> ---
> MAINTAINERS | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index ea3e6c914384..f0485f61295d 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15972,14 +15972,6 @@ F: Documentation/devicetree/bindings/misc/qcom,fastrpc.txt
> F: drivers/misc/fastrpc.c
> F: include/uapi/misc/fastrpc.h
>
> -QUALCOMM GENERIC INTERFACE I2C DRIVER
> -M: Akash Asthana <akashast@codeaurora.org>
> -M: Mukesh Savaliya <msavaliy@codeaurora.org>
> -L: linux-i2c@vger.kernel.org
> -L: linux-arm-msm@vger.kernel.org
> -S: Supported
> -F: drivers/i2c/busses/i2c-qcom-geni.c
> -
> QUALCOMM HEXAGON ARCHITECTURE
> M: Brian Cain <bcain@codeaurora.org>
> L: linux-hexagon@vger.kernel.org
> --
> 2.30.2
>
next prev parent reply other threads:[~2022-02-18 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 10:49 [PATCH] MAINTAINERS: remove duplicate entry for i2c-qcom-geni Wolfram Sang
2022-02-18 17:52 ` Bjorn Andersson [this message]
2022-02-18 21:11 ` Wolfram Sang
2022-02-19 11:46 ` Wolfram Sang
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=Yg/c+27yR1P0b+eL@ripper \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@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).