public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: 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 08:14:33 -0700	[thread overview]
Message-ID: <a3ffaea6a161e667854127d2e021a04034985a97.camel@perches.com> (raw)
In-Reply-To: <20180410144654.fg2pbvh4d2y3rucv@katana>

On Tue, 2018-04-10 at 16:46 +0200, Wolfram Sang wrote:
> > 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.

I believe get_maintainer.pl is still going to do that for
awhile as you are a commit signer for several of these driver
files.  Files that are not either "supported" or "maintained"
by default add the --git-fallback option.

For instance, With your patch:
$ ./scripts/get_maintainer.pl -f drivers/i2c/algos/i2c-algo-bit.c
Wolfram Sang <wsa+renesas@sang-engineering.com> (commit_signer:3/2=100%,authored:1/2=50%,added_lines:5/15=33%)
Jean Delvare <jdelvare@suse.de> (commit_signer:1/2=50%,authored:1/2=50%,added_lines:10/15=67%,removed_lines:3/3=100%)
linux-i2c@vger.kernel.org (open list:I2C SUBSYSTEM DRIVERS)
linux-kernel@vger.kernel.org (open list)

Your name should not be shown after a year or so unless you
actually sign-off on patches to those subdirectories.

btw: You signed-off using 2 different addresses on one
of those patches.  I think that's odd.

commit 3e5f06bed72fe72166a6778f630241a893f67799
Author: Wolfram Sang <wsa+renesas@sang-engineering.com>
Date:   Mon Dec 4 09:16:18 2017 +0100

    i2c: algo-bit: init the bus to a known state
    
    Ensure the bus is free when we register the adapter. Before the SCL/SDA
    wires were in an unknown state. It used to work because sending a byte
    has a retry mechanism which was triggered if the bus was initially in a
    non-free state. But the graceful way to do it is to initialize
    correctly.
    
    Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
    Signed-off-by: Wolfram Sang <wsa@the-dreams.de>

  reply	other threads:[~2018-04-10 15:14 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
2018-04-10 15:14     ` Joe Perches [this message]
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=a3ffaea6a161e667854127d2e021a04034985a97.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