All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Tony Lindgren <tony@atomide.com>
Cc: soc@kernel.org
Subject: Re: [GIT PULL 1/3] Non-urgent driver fix for ti-sysc for v6.5
Date: Tue, 06 Jun 2023 20:40:24 +0000	[thread overview]
Message-ID: <168608402444.20407.2211950353872412569.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <pull-1685700720-242492@atomide.com>

Hello:

This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:

On Fri,  2 Jun 2023 13:13:05 +0300 you wrote:
> From: "Tony Lindgren" <tony@atomide.com>
> 
> The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
> 
>   Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
> 
> are available in the Git repository at:
> 
> [...]

Here is the summary with links:
  - [GIT,PULL,1/3] Non-urgent driver fix for ti-sysc for v6.5
    (no matching commit)
  - [GIT,PULL,2/3] Clean-up for omap pinctrl-single nodes for v6.5
    (no matching commit)
  - [GIT,PULL,3/3] Devicetree changes for omaps for v6.5
    https://git.kernel.org/soc/soc/c/c5c3f746c9ba

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2023-06-06 20:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 10:13 [GIT PULL 1/3] Non-urgent driver fix for ti-sysc for v6.5 Tony Lindgren
2023-06-02 10:13 ` Tony Lindgren
2023-06-02 10:13 ` [GIT PULL 2/3] Clean-up for omap pinctrl-single nodes " Tony Lindgren
2023-06-02 10:13   ` Tony Lindgren
2023-06-02 10:13 ` [GIT PULL 3/3] Devicetree changes for omaps " Tony Lindgren
2023-06-02 10:13   ` Tony Lindgren
2023-06-06 20:40 ` patchwork-bot+linux-soc [this message]
2023-06-09 13:10 ` [GIT PULL 1/3] Non-urgent driver fix for ti-sysc " 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=168608402444.20407.2211950353872412569.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.