From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Tony Lindgren" <tony@atomide.com>
Subject: [GIT PULL 1/3] Non-urgent driver fix for ti-sysc for v6.5
Date: Fri, 2 Jun 2023 13:13:05 +0300 [thread overview]
Message-ID: <pull-1685700720-242492@atomide.com> (raw)
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:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v6.5/ti-sysc-signed
for you to fetch changes up to f620596fa347170852da499e778a5736d79a4b79:
bus: ti-sysc: Fix dispc quirk masking bool variables (2023-05-17 10:17:01 +0300)
----------------------------------------------------------------
Non-urgent ti-sysc driver fix for v6.5 merge window
A fix for masking bool variables that can wait for the merge window
no problem.
----------------------------------------------------------------
Tony Lindgren (1):
bus: ti-sysc: Fix dispc quirk masking bool variables
drivers/bus/ti-sysc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Tony Lindgren" <tony@atomide.com>
Subject: [GIT PULL 1/3] Non-urgent driver fix for ti-sysc for v6.5
Date: Fri, 2 Jun 2023 13:13:05 +0300 [thread overview]
Message-ID: <pull-1685700720-242492@atomide.com> (raw)
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:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v6.5/ti-sysc-signed
for you to fetch changes up to f620596fa347170852da499e778a5736d79a4b79:
bus: ti-sysc: Fix dispc quirk masking bool variables (2023-05-17 10:17:01 +0300)
----------------------------------------------------------------
Non-urgent ti-sysc driver fix for v6.5 merge window
A fix for masking bool variables that can wait for the merge window
no problem.
----------------------------------------------------------------
Tony Lindgren (1):
bus: ti-sysc: Fix dispc quirk masking bool variables
drivers/bus/ti-sysc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-06-02 10:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 10:13 Tony Lindgren [this message]
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 ` [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 ` [GIT PULL 1/3] Non-urgent driver fix for ti-sysc " patchwork-bot+linux-soc
2023-06-09 13:10 ` 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=pull-1685700720-242492@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=soc@kernel.org \
/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.