From: "Arnd Bergmann" <arnd@arndb•de>
To: "Lukas Bulwahn" <lbulwahn@redhat•com>,
"Mark Brown" <broonie@kernel•org>,
linux-arm-kernel@lists•infradead.org,
linux-sound@vger•kernel.org
Cc: "Daniel Mack" <daniel@zonque•org>,
"Haojian Zhuang" <haojian.zhuang@gmail•com>,
"Robert Jarzmik" <robert.jarzmik@free•fr>,
"Liam Girdwood" <lgirdwood@gmail•com>,
"Jaroslav Kysela" <perex@perex•cz>,
"Takashi Iwai" <tiwai@suse•com>,
kernel-janitors@vger•kernel.org, linux-kernel@vger•kernel.org,
"Lukas Bulwahn" <lukas.bulwahn@redhat•com>
Subject: Re: [PATCH] MAINTAINERS: drop obsolete file entry in PXA2xx/PXA3xx SUPPORT
Date: Tue, 19 May 2026 11:39:10 +0200 [thread overview]
Message-ID: <ae162faa-d42a-4075-829b-8d554b1c3064@app.fastmail.com> (raw)
In-Reply-To: <20260519090720.301782-1-lukas.bulwahn@redhat.com>
On Tue, May 19, 2026, at 11:07, Lukas Bulwahn wrote:
> From: Lukas Bulwahn <lukas.bulwahn@redhat•com>
>
> Commit 42f67e1d1cba ("ASoC: pxa: integrate sound/arm/pxa2xx into
> sound/soc/pxa2xx") moves all files matching sound/arm/pxa* into
> sound/soc/pxa/. Hence, the file entry in referring to sound/arm/pxa* does
> not match any file in the repository anymore. As the PXA2xx/PXA3xx SUPPORT
> section already contains a file entry referring to sound/soc/pxa/, the
> moved files are already matched by the existing file entries.
>
> Simply drop the obsolete file entry in PXA2xx/PXA3xx SUPPORT.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@redhat•com>
Thanks!
Acked-by: Arnd Bergmann <arnd@arndb•de>
prev parent reply other threads:[~2026-05-19 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 9:07 [PATCH] MAINTAINERS: drop obsolete file entry in PXA2xx/PXA3xx SUPPORT Lukas Bulwahn
2026-05-19 9:39 ` Arnd Bergmann [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=ae162faa-d42a-4075-829b-8d554b1c3064@app.fastmail.com \
--to=arnd@arndb$(echo .)de \
--cc=broonie@kernel$(echo .)org \
--cc=daniel@zonque$(echo .)org \
--cc=haojian.zhuang@gmail$(echo .)com \
--cc=kernel-janitors@vger$(echo .)kernel.org \
--cc=lbulwahn@redhat$(echo .)com \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-sound@vger$(echo .)kernel.org \
--cc=lukas.bulwahn@redhat$(echo .)com \
--cc=perex@perex$(echo .)cz \
--cc=robert.jarzmik@free$(echo .)fr \
--cc=tiwai@suse$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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