All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	"Joe Perches" <joe@perches.com>,
	"Ralf Ramsauer" <ralf.ramsauer@oth-regensburg.de>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: remove obsolete OMAP HWMOD DATA FOR OMAP4-BASED DEVICES
Date: Wed, 31 Mar 2021 09:41:28 +0300	[thread overview]
Message-ID: <YGQZmIsbXnuIX5S4@atomide.com> (raw)
In-Reply-To: <20210318172520.6634-1-lukas.bulwahn@gmail.com>

* Lukas Bulwahn <lukas.bulwahn@gmail.com> [210318 19:26]:
> Commit 2584d7e7f87a ("ARM: OMAP2+: Drop legacy platform data for omap4
> hwmod") drops the file ./arch/arm/mach-omap2/omap_hwmod_44xx_data.c, but
> misses to drop the now obsolete OMAP HWMOD DATA FOR OMAP4-BASED DEVICES
> section in MAINTAINERS, which refers to only that file.
> 
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains:
> 
>   warning: no file matches  F:  arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> 
> Remove the obsolete OMAP HWMOD DATA FOR OMAP4-BASED DEVICES section.

Thanks applying into omap-for-v5.13/genpd-cleanup.

Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	"Joe Perches" <joe@perches.com>,
	"Ralf Ramsauer" <ralf.ramsauer@oth-regensburg.de>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: remove obsolete OMAP HWMOD DATA FOR OMAP4-BASED DEVICES
Date: Wed, 31 Mar 2021 09:41:28 +0300	[thread overview]
Message-ID: <YGQZmIsbXnuIX5S4@atomide.com> (raw)
In-Reply-To: <20210318172520.6634-1-lukas.bulwahn@gmail.com>

* Lukas Bulwahn <lukas.bulwahn@gmail.com> [210318 19:26]:
> Commit 2584d7e7f87a ("ARM: OMAP2+: Drop legacy platform data for omap4
> hwmod") drops the file ./arch/arm/mach-omap2/omap_hwmod_44xx_data.c, but
> misses to drop the now obsolete OMAP HWMOD DATA FOR OMAP4-BASED DEVICES
> section in MAINTAINERS, which refers to only that file.
> 
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains:
> 
>   warning: no file matches  F:  arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> 
> Remove the obsolete OMAP HWMOD DATA FOR OMAP4-BASED DEVICES section.

Thanks applying into omap-for-v5.13/genpd-cleanup.

Tony

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-03-31  6:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 17:25 [PATCH] MAINTAINERS: remove obsolete OMAP HWMOD DATA FOR OMAP4-BASED DEVICES Lukas Bulwahn
2021-03-18 17:25 ` Lukas Bulwahn
2021-03-31  6:41 ` Tony Lindgren [this message]
2021-03-31  6:41   ` Tony Lindgren

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=YGQZmIsbXnuIX5S4@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=joe@perches.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=ralf.ramsauer@oth-regensburg.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.