From: patchwork-bot+linux-soc@kernel.org
To: Tony Lindgren <tony@atomide.com>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] Devicetree related musb changes for omap3 for v6.2
Date: Wed, 30 Nov 2022 17:11:02 +0000 [thread overview]
Message-ID: <166982826207.9936.9821955450100740887.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <pull-1669364566-84575@atomide.com>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Fri, 25 Nov 2022 10:23:12 +0200 you wrote:
> From: "Tony Lindgren" <tony@atomide.com>
>
> The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
>
> Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
>
> are available in the Git repository at:
>
> [...]
Here is the summary with links:
- [GIT,PULL] Devicetree related musb changes for omap3 for v6.2
https://git.kernel.org/soc/soc/c/799423ec5a6d
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-11-30 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 8:23 [GIT PULL] Devicetree related musb changes for omap3 for v6.2 Tony Lindgren
2022-11-25 8:23 ` Tony Lindgren
2022-11-30 17:11 ` 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=166982826207.9936.9821955450100740887.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=soc@kernel.org \
--cc=tony@atomide.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 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.