linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Wolfram Sang <wsa@kernel.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Jarkko Nikula <jarkko.nikula@linux.intel.com>,
	Lee Jones <lee.jones@linaro.org>,
	linux-i2c <linux-i2c@vger.kernel.org>,
	Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>,
	kernel-janitors <kernel-janitors@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: adjust to removing i2c designware platform data
Date: Fri, 28 May 2021 16:54:06 +0200	[thread overview]
Message-ID: <CAKXUXMwB5-7b8XsO=3jq2VxMf-C92VSYBTCArkLF+hhkKWHSzw@mail.gmail.com> (raw)
In-Reply-To: <YLECsC9y8ici47Ln@kunai>

On Fri, May 28, 2021 at 4:48 PM Wolfram Sang <wsa@kernel.org> wrote:
>
>
> > > > Remove the file entry to this removed file as well.
> > >
> > > Oops, I was under the impression I grepped all occurrences, but I have not.
> > >
> > > Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> > >
> > > Thanks for the catch!
> >
> > Wolfram, isn't it forgotten somehow?
>
> I can pick it. I refrained from doing so because Lukas explicitly asked
> Lee to pick it.
>

Wolfram, take it. Nobody compiles MAINTAINERS, so it cannot break any build :)

Thanks, Lukas

  reply	other threads:[~2021-05-28 14:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19  6:18 [PATCH] MAINTAINERS: adjust to removing i2c designware platform data Lukas Bulwahn
2021-04-19  8:33 ` Andy Shevchenko
2021-05-28 14:34   ` Andy Shevchenko
2021-05-28 14:48     ` Wolfram Sang
2021-05-28 14:54       ` Lukas Bulwahn [this message]
2021-05-28 17:19       ` Andy Shevchenko
2021-05-28 18:19         ` Lee Jones
2021-05-29  7:49           ` Andy Shevchenko
2021-05-28 14: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='CAKXUXMwB5-7b8XsO=3jq2VxMf-C92VSYBTCArkLF+hhkKWHSzw@mail.gmail.com' \
    --to=lukas.bulwahn@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=ralf.ramsauer@oth-regensburg.de \
    --cc=wsa@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;
as well as URLs for NNTP newsgroup(s).