linux-kernel - Re: [PATCH] MAINTAINERS: remove me as maintainer for I2C host drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <695c3bd58a41b1f902c0deabf7552fcd5a89b53f.camel@perches.com>
Date:   Tue, 10 Apr 2018 09:47:38 -0700
From:   Joe Perches <joe@...ches.com>
To:     Peter Rosin <peda@...ntia.se>, Wolfram Sang <wsa@...-dreams.de>
Cc:     linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: remove me as maintainer for I2C host
 drivers

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@...r.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/