From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Prabhakar <prabhakar.csengg@gmail.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: (subset) [PATCH v2 0/4] ASoC: Rename "sh" to "renesas"
Date: Wed, 30 Oct 2024 17:33:25 +0000 [thread overview]
Message-ID: <173030960575.47565.8642908842032187075.b4-ty@kernel.org> (raw)
In-Reply-To: <20241021201349.395022-1-prabhakar.mahadev-lad.rj@bp.renesas.com>
On Mon, 21 Oct 2024 21:13:45 +0100, Prabhakar wrote:
> This patch series aims to rename "sh" to "renesas", along with this
> the references to this path have been updated.
>
> Note,
> - This patch series applies on top of [0] + [1]
> - This change was agrreed based on the discussion [2]
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/4] ASoC: Rename "sh" to "renesas"
commit: c0aba02cdc1afde6c2349db95ad36b9532b42a37
[2/4] ASoC: renesas, rsnd: Update file path
commit: 94c0a8a10f05782a4426a67343e3081601ad3f1a
[3/4] ASoC: audio-graph-card2: Update comment with renamed file path
commit: 1b3130e9e77e4286a2e495b4b3c3efcf54848633
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2024-10-30 17:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 20:13 Prabhakar
2024-10-21 20:13 ` [PATCH v2 1/4] " Prabhakar
2024-10-21 20:13 ` [PATCH v2 2/4] ASoC: renesas, rsnd: Update file path Prabhakar
2024-10-21 20:13 ` [PATCH v2 3/4] ASoC: audio-graph-card2: Update comment with renamed " Prabhakar
2024-10-21 20:13 ` [PATCH v2 4/4] MAINTAINERS: Add entry for Renesas ASoC drivers Prabhakar
2024-10-22 18:33 ` Mark Brown
2024-10-22 23:21 ` Kuninori Morimoto
2024-10-22 23:20 ` Kuninori Morimoto
2024-10-23 6:57 ` Biju Das
2024-10-25 10:54 ` Lad, Prabhakar
2024-10-25 10:53 ` Lad, Prabhakar
2024-10-30 17:33 ` Mark Brown [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=173030960575.47565.8642908842032187075.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=tiwai@suse.com \
/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
all inboxes | Powered by JetHome®