From: patchwork-bot+linux-soc@kernel.org
To: Sven Peter <sven@svenpeter.dev>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] Apple SoC RTKit/SART/NVMe driver
Date: Thu, 05 May 2022 19:31:48 +0000 [thread overview]
Message-ID: <165177910801.9627.12656188073939134308.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220505154020.84638-1-sven@svenpeter.dev>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Thu, 5 May 2022 17:40:20 +0200 you wrote:
> Hi SoC Team,
>
> Please merge the Apple SoC NVMe driver and its dependencies for 5.19.
> As discussed on the nvme mailing list [1] it's easiest if we take it
> entirely through the SoC tree since there's a chance that we will have
> more drivers depending on rtkit for 5.19.
>
> [...]
Here is the summary with links:
- [GIT,PULL] Apple SoC RTKit/SART/NVMe driver
https://git.kernel.org/soc/soc/c/bdc33dad34be
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-05-05 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 15:40 [GIT PULL] Apple SoC RTKit/SART/NVMe driver Sven Peter
2022-05-05 15:40 ` Sven Peter
2022-05-05 19:31 ` patchwork-bot+linux-soc [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=165177910801.9627.12656188073939134308.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=soc@kernel.org \
--cc=sven@svenpeter.dev \
/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.