From: Joe Perches <joe@perches.com>
To: Wolfram Sang <wsa@the-dreams.de>, linux-i2c@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: remove me as maintainer for I2C host drivers
Date: Tue, 10 Apr 2018 07:33:25 -0700 [thread overview]
Message-ID: <f0ce07bdb69602450ea1681936706b16962ce41f.camel@perches.com> (raw)
In-Reply-To: <20180410141125.4477-1-wsa@the-dreams.de>
On Tue, 2018-04-10 at 16:11 +0200, Wolfram Sang wrote:
> The number of I2C host controller drivers keeps increasing, and although
> I had some success acquiring specific driver maintainers, my bandwidth
> is by far not enough to act as a fallback for the rest of the drivers.
> To reflect this status-quo in MAINTAINERS, add a seperate entry for I2C
> host drivers, let the I2C list (= community) be the contact point, and
> mark this section as "Odd fixes".
>
> Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
> ---
>
> Joe: my tests worked fine with the file patterns; yet I'd appreciate if you
> had time to double check them. Thanks!
Hi Wolfram.
As far as I understand, all this seems correct to me.
You want to maintain the core files in drivers/i2c/
but not any files in any of algos/, busses/, or muxes/.
You might also want to specify which of the
include/linux/i2c-*.h files you actually want to oversee
as well. It seems some are driver specific.
But the git entry for the drivers seems maybe a bit of
an issue. Are you
intending to somehow pick up patches
approved by the i2c community? If
not, no worries I
guess, someone might come along to provide help.
cheers, Joe
> MAINTAINERS | 14 +++++++++++---
> 1 file changed, 11 insertions(+), 3 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 6d296bdce328..2f7ccdcf76f7 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -6580,15 +6580,23 @@ W: https://i2c.wiki.kernel.org/
> Q: https://patchwork.ozlabs.org/project/linux-i2c/list/
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git
> S: Maintained
> -F: Documentation/devicetree/bindings/i2c/
> +F: Documentation/devicetree/bindings/i2c/i2c.txt
> F: Documentation/i2c/
> -F: drivers/i2c/
> -F: drivers/i2c/*/
> +F: drivers/i2c/*
> F: include/linux/i2c.h
> F: include/linux/i2c-*.h
> F: include/uapi/linux/i2c.h
> F: include/uapi/linux/i2c-*.h
>
> +I2C SUBSYSTEM DRIVERS
> +L: linux-i2c@vger.kernel.org
> +W: https://i2c.wiki.kernel.org/
> +Q: https://patchwork.ozlabs.org/project/linux-i2c/list/
> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git
> +S: Odd Fixes
> +F: Documentation/devicetree/bindings/i2c/
> +F: drivers/i2c/*/
> +
> I2C-TAOS-EVM DRIVER
> M: Jean Delvare <jdelvare@suse.com>
> L: linux-i2c@vger.kernel.org
next prev parent reply other threads:[~2018-04-10 14:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 14:11 [PATCH] MAINTAINERS: remove me as maintainer for I2C host drivers Wolfram Sang
2018-04-10 14:33 ` Joe Perches [this message]
2018-04-10 14:46 ` Wolfram Sang
2018-04-10 15:14 ` Joe Perches
2018-04-10 15:25 ` Wolfram Sang
2018-04-10 15:40 ` Peter Rosin
2018-04-10 15:52 ` Wolfram Sang
2018-04-10 16:42 ` Peter Rosin
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=f0ce07bdb69602450ea1681936706b16962ce41f.camel@perches.com \
--to=joe@perches.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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