All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Federico Vaga <federico.vaga@cern.ch>,
	Denis Efremov <efremov@linux.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Pat Riehecky <riehecky@fnal.gov>,
	Alessandro Rubini <rubini@gnudd.com>,
	Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>,
	Sebastian Duda <sebastian.duda@fau.de>
Subject: Re: [PATCH] fmc: remove left-over ipmi-fru.h after fmc deletion
Date: Tue, 7 Jan 2020 00:05:02 +0100	[thread overview]
Message-ID: <CACRpkdaY6jCdSpdDejo87CgoO6qbekj-QO354a1K0BeHYOnCpw@mail.gmail.com> (raw)
In-Reply-To: <20191214114913.8610-1-lukas.bulwahn@gmail.com>

On Sat, Dec 14, 2019 at 12:49 PM Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:

> Commit 6a80b30086b8 ("fmc: Delete the FMC subsystem") from Linus Walleij
> deleted the obsolete FMC subsystem, but missed the MAINTAINERS entry and
> include/linux/ipmi-fru.h mentioned in the MAINTAINERS entry.
>
> Later, commit d5d4aa1ec198 ("MAINTAINERS: Remove FMC subsystem") from
> Denis Efremov cleaned up the MAINTAINERS entry, but actually also missed
> that include/linux/ipmi-fru.h should also be deleted while deleting its
> reference in MAINTAINERS.
>
> So, deleting include/linux/ipmi-fru.h slipped through the previous
> clean-ups.
>
> As there is no further use for include/linux/ipmi-fru.h, finally delete
> include/linux/ipmi-fru.h for good now.
>
> Fixes: d5d4aa1ec198 ("MAINTAINERS: Remove FMC subsystem")
> Fixes: 6a80b30086b8 ("fmc: Delete the FMC subsystem")
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> Linus, please pick this patch.

OK applied this to the GPIO tree, thanks!

Yours,
Linus Walleij

      parent reply	other threads:[~2020-01-06 23:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-14 11:49 [PATCH] fmc: remove left-over ipmi-fru.h after fmc deletion Lukas Bulwahn
2019-12-16  8:51 ` Federico Vaga
2020-01-06 23:05 ` Linus Walleij [this message]

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=CACRpkdaY6jCdSpdDejo87CgoO6qbekj-QO354a1K0BeHYOnCpw@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=efremov@linux.com \
    --cc=federico.vaga@cern.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=ralf.ramsauer@oth-regensburg.de \
    --cc=riehecky@fnal.gov \
    --cc=rubini@gnudd.com \
    --cc=sebastian.duda@fau.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.