From: patchwork-bot+linux-soc@kernel.org
To: Tony Lindgren <tony@atomide.com>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] Fixes for omaps
Date: Fri, 25 Feb 2022 15:50:11 +0000 [thread overview]
Message-ID: <164580421131.25553.13852413575112824598.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <pull-1645606483-876944@atomide.com>
Hello:
This pull request was applied to soc/soc.git (arm/fixes)
by Arnd Bergmann <arnd@arndb.de>:
On Wed, 23 Feb 2022 10:55:39 +0200 you wrote:
> From: "Tony Lindgren" <tony@atomide.com>
>
> The following changes since commit 486343d3728be741db13854dc7e983c20cdd7c07:
>
> Merge tag 'omap-for-v5.17/fixes-for-merge-window-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into arm/fixes (2022-02-07 17:42:44 +0100)
>
> are available in the Git repository at:
>
> [...]
Here is the summary with links:
- [GIT,PULL] Fixes for omaps
https://git.kernel.org/soc/soc/c/f03f10a9823a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-02-25 15:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 8:55 [GIT PULL] Fixes for omaps Tony Lindgren
2022-02-25 15:50 ` patchwork-bot+linux-soc [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-08 12:17 Tony Lindgren
2023-12-21 17:40 ` patchwork-bot+linux-soc
2023-12-21 17:41 ` patchwork-bot+linux-soc
2023-10-18 5:19 Tony Lindgren
2023-10-18 15:40 ` patchwork-bot+linux-soc
2023-10-18 15:40 ` patchwork-bot+linux-soc
2023-08-16 4:02 Tony Lindgren
2023-08-17 12:50 ` patchwork-bot+linux-soc
2023-08-17 12:50 ` patchwork-bot+linux-soc
2022-04-21 12:15 Tony Lindgren
2022-04-21 15:30 ` patchwork-bot+linux-soc
2022-04-21 15:31 ` patchwork-bot+linux-soc
2022-01-10 7:55 Tony Lindgren
2022-01-10 18:40 ` patchwork-bot+linux-soc
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=164580421131.25553.13852413575112824598.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).