From: Palmer Dabbelt <palmer@dabbelt.com>
To: schwab@linux-m68k.org
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 15:12:30 -0800 (PST) [thread overview]
Message-ID: <mhng-6cc11053-b031-4ee5-875f-fa18095839db@palmer-ri-x1c9> (raw)
In-Reply-To: <87mtm9rp35.fsf@igel.home>
On Fri, 12 Nov 2021 14:22:54 PST (-0800), schwab@linux-m68k.org wrote:
> 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?
Sorry, I hadn't seen that one. I found some bugs in my test suite when
getting it to run on the new machines so I've got some new failures I'm
working through, which is sort of blocking up everything right now.
Everything in this PR was tested the old way so I'm confident in it, but
I usually do a merge with Linus' tree and test that before sending a PR.
In hindsight it might have been better to skip that this time around,
given all the headaches getting things up and running, but it's too late
for that now.
I'd like to get back on a more solid footing before trying to pick up
more stuff -- I guess that's a pretty trivial fix, but anything in the
build system can run into wrinkles (also looks like it was broken in
5.15, so it'll have to get backported).
next prev parent reply other threads:[~2021-11-12 23:12 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
2021-11-12 23:12 ` Palmer Dabbelt [this message]
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=mhng-6cc11053-b031-4ee5-875f-fa18095839db@palmer-ri-x1c9 \
--to=palmer@dabbelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=schwab@linux-m68k.org \
--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;
as well as URLs for NNTP newsgroup(s).