From: Wolfram Sang <wsa@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.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 22:11:39 +0100 [thread overview]
Message-ID: <YhALi4X78OzJbjs9@kunai> (raw)
In-Reply-To: <Yg/c+27yR1P0b+eL@ripper>
[-- Attachment #1: Type: text/plain, Size: 191 bytes --]
> It would have been nice to go the other direction (reducing
> ARM/QUALCOMM), but your assessment looks accurate, so:
I totally agree. Sadly, I don't know who could take over the driver.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-02-18 21:11 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
2022-02-18 21:11 ` Wolfram Sang [this message]
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=YhALi4X78OzJbjs9@kunai \
--to=wsa@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.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).