From: Andreas Schwab <schwab@linux-m68k.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [GIT PULL] RISC-V Patches for the 5.16 Merge Window, Part 1
Date: Fri, 12 Nov 2021 23:22:54 +0100 [thread overview]
Message-ID: <87mtm9rp35.fsf@igel.home> (raw)
In-Reply-To: <mhng-8aed9afb-1b05-413b-9808-5d0936c9f131@palmer-ri-x1c9> (Palmer Dabbelt's message of "Fri, 12 Nov 2021 13:52:46 -0800 (PST)")
On Nov 12 2021, Palmer Dabbelt wrote:
> I wasn't planning on sending anything else for the merge window.
Not even the KBUILD_EXTMOD build fix?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2021-11-12 22:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 17:32 [GIT PULL] RISC-V Patches for the 5.16 Merge Window, Part 1 Palmer Dabbelt
2021-11-12 17:42 ` Palmer Dabbelt
2021-11-12 21:37 ` Linus Torvalds
2021-11-12 21:52 ` Palmer Dabbelt
2021-11-12 22:22 ` Andreas Schwab [this message]
2021-11-12 23:12 ` Palmer Dabbelt
2021-11-13 19:15 ` pr-tracker-bot
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=87mtm9rp35.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=torvalds@linux-foundation.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