From: Wolfram Sang <wsa@the-dreams.de>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Jean Delvare <jdelvare@suse.com>,
linux-i2c <linux-i2c@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mukesh Ojha <mojha@codeaurora.org>
Subject: Re: [PATCH] i2c: isch: Remove unnecessary acpi.h include
Date: Mon, 1 Apr 2019 21:45:59 +0200 [thread overview]
Message-ID: <20190401194558.zdcr3m3imd6vpze6@ninjato> (raw)
In-Reply-To: <CAErSpo6MJFJO3s4NZ61CPZngbSaOhG-s5wLJyCQbwvdcnuBP1Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
> > > Jean, would you like me to repost this with the updates? I assume you
> > > will merge this (just based on get_maintainer.pl)?
> >
> > I will apply it, now that it has Jean's Rev-by. I assume this is
> > for-next material despite the Fixes tag?
>
> Definitely for-next material, not for the current release. Jean
> suggested the Fixes tag, I think since it's related to a specific
> commit and could be backported together with that commit.
Makes sense.
> Should there be a MAINTAINERS update to clarify who applies patches to
> drivers/i2c/busses/i2c-isch.c? Right now, get_maintainers.pl doesn't
> mention you (Wolfram).
I have set the i2c/busses directory to 'Odd Fixes' in MAINTAINERS. I
don't want to be mentioned for specific drivers. I am eagerly looking
for driver maintainers to spread reponsibility. Maybe my tree could be
added to Jean's maintainer entry, but not sure what that is worth...
> Patch with tags attached in case it's useful to you (sorry, I'm
> saddled with gmail right now and can't include it inline).
No worries. Patchwork keeps it all for me.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-04-01 19:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 18:36 [PATCH] i2c: isch: Remove unnecessary acpi.h include helgaas
2019-03-31 8:36 ` Jean Delvare
2019-03-31 9:31 ` Mukesh Ojha
2019-04-01 13:50 ` Bjorn Helgaas
2019-04-01 14:08 ` Wolfram Sang
2019-04-01 19:37 ` Bjorn Helgaas
2019-04-01 19:45 ` Wolfram Sang [this message]
2019-04-03 20:57 ` Wolfram Sang
2019-04-03 22:27 ` Bjorn Helgaas
2019-04-01 15:07 ` Jean Delvare
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=20190401194558.zdcr3m3imd6vpze6@ninjato \
--to=wsa@the-dreams.de \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mojha@codeaurora.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