From: Wolfram Sang <wsa@the-dreams.de>
To: Joe Perches <joe@perches.com>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: remove me as maintainer for I2C host drivers
Date: Tue, 10 Apr 2018 16:46:54 +0200 [thread overview]
Message-ID: <20180410144654.fg2pbvh4d2y3rucv@katana> (raw)
In-Reply-To: <f0ce07bdb69602450ea1681936706b16962ce41f.camel@perches.com>
[-- Attachment #1: Type: text/plain, Size: 952 bytes --]
> As far as I understand, all this seems correct to me.
Good. Thank you, Joe!
> You want to maintain the core files in drivers/i2c/
> but not any files in any of algos/, busses/, or muxes/.
More specific: I don't want get_maintainer.pl to print me as a
maintainer for these drivers. This gives a wrong impression to users. I
am not actively maintaining these drivers, I am collecting the odd
fixes (and also review some of them as time permits).
> 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.
I am just now working on that. Most of them can easily be moved to
platform_data.
> 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?
Yes, I will still be doing that. I think I will also be the one doing
most review for those odd fixes nonetheless.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-10 14:46 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
2018-04-10 14:46 ` Wolfram Sang [this message]
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=20180410144654.fg2pbvh4d2y3rucv@katana \
--to=wsa@the-dreams.de \
--cc=joe@perches.com \
--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