From: "Gabriel L. Somlo" <gsomlo@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
soc@kernel.org, LKML <linux-kernel@vger.kernel.org>,
Karol Gugala <kgugala@antmicro.com>,
Mateusz Holenko <mholenko@antmicro.com>,
Joel Stanley <joel@jms.id.au>, Andrew Davis <afd@ti.com>
Subject: Re: [GIT PULL] LiteX updates for next
Date: Mon, 20 Jan 2025 09:30:34 -0500 [thread overview]
Message-ID: <Z45eCnu8QwJrO_Ry@errol.ini.cmu.edu> (raw)
In-Reply-To: <Z41PgCffqPUTyxkE@errol.ini.cmu.edu>
Hi Arnd,
Sorry for the n00b question, but I just saw that 6.13 came out right
after I sent you this PR :)
What's the right thing to do in this situation? Wait for 6.14-rc1 and
try again? Something else ?
Thanks, as always,
--Gabriel
On Sun, Jan 19, 2025 at 02:16:16PM -0500, Gabriel L. Somlo wrote:
> Hi Arnd,
>
> The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:
>
> Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)
>
> are available in the Git repository at:
>
> https://github.com/litex-hub/linux.git tags/litex-6.13-rc1
>
> for you to fetch changes up to c7345869aa382b1e22691d51cbbd218d7f488a55:
>
> drivers/soc/litex: Use devm_register_restart_handler() (2025-01-19 14:05:35 -0500)
>
> ----------------------------------------------------------------
> LiteX updates for next
>
> Remaining LiteX updates from 2024, reviewed and
> successfully tested against v6.13-rc1.
>
> Signed-off-by: Gabriel Somlo <gsomlo@gmail.com>
>
> ----------------------------------------------------------------
> Andrew Davis (1):
> drivers/soc/litex: Use devm_register_restart_handler()
>
> drivers/soc/litex/litex_soc_ctrl.c | 23 +++++------------------
> 1 file changed, 5 insertions(+), 18 deletions(-)
prev parent reply other threads:[~2025-01-20 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-19 19:16 Gabriel L. Somlo
2025-01-20 14:30 ` Gabriel L. Somlo [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=Z45eCnu8QwJrO_Ry@errol.ini.cmu.edu \
--to=gsomlo@gmail.com \
--cc=afd@ti.com \
--cc=arnd@arndb.de \
--cc=joel@jms.id.au \
--cc=kgugala@antmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mholenko@antmicro.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®