From: Joe Perches <joe@perches.com>
To: Peter Rosin <peda@axentia.se>, Wolfram Sang <wsa@the-dreams.de>
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 09:47:38 -0700 [thread overview]
Message-ID: <695c3bd58a41b1f902c0deabf7552fcd5a89b53f.camel@perches.com> (raw)
In-Reply-To: <29ab4b56-f857-a2d6-0b28-833896e9f47c@axentia.se>
On Tue, 2018-04-10 at 18:42 +0200, Peter Rosin wrote:
> On 2018-04-10 17:52, Wolfram Sang wrote:
> > Hi Peter,
> >
> > > Hmm, I think you are ducking out from the i2c-mux-pinctrl driver as well.
> > > Was that the intent?
> >
> > Oops, nope! Sorry, I just forgot about the demux (I think you mean that
> > one) driver and will create a seperate entry for it.
>
> Right, I meant the demux...
>
> > >
> > > > +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/*/
> > > > +
> > >
> > > And this includes all the other muxes, i.e. those that are "mine". Maybe
> > > not a problem, but what do I know?
> >
> > Sorry again, I really didn't want to dump something on you or leave you
> > all alone with the muxes. I was just so focussed on the host drivers
> > that muxes simply slipped through my mind :( I can add myself to the
> > muxes section again, no problem. I'll let you decidei what you prefer,
> > both is fine for me. You are doing a great job there!
>
> No no, you don't need to add yourself there. I understand the mux drivers,
> and it's pretty quiet, so no need for that. What I was worrying about was
> this "Odd Fixes" fallback entry needlessly covering the muxes when they
> are covered elsewhere.
If you want to exclude drivers/i2c/muxes from the
subsystem drivers block then you could add
X: drivers/i2c/muxes/
next prev parent reply other threads:[~2018-04-10 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 14:11 Wolfram Sang
2018-04-10 14:33 ` Joe Perches
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
2018-04-10 16:47 ` Joe Perches [this message]
2018-04-10 16:49 ` 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=695c3bd58a41b1f902c0deabf7552fcd5a89b53f.camel@perches.com \
--to=joe@perches.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--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
all inboxes | Powered by JetHome®