[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <mhng-036eff83-1a93-4e98-9810-a4abb79e55e7@palmer-ri-x1c9a>
Date: Fri, 28 Oct 2022 15:23:21 -0700 (PDT)
From: Palmer Dabbelt <palmer@...belt.com>
To: Conor Dooley <conor.dooley@...rochip.com>
CC: waterdev@...axycrow.de, Conor Dooley <conor@...nel.org>,
Paul Walmsley <paul.walmsley@...ive.com>,
aou@...s.berkeley.edu, linux-riscv@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] riscv: fix styling in ucontext header
On Wed, 19 Oct 2022 03:20:44 PDT (-0700), Conor Dooley wrote:
> On Wed, Oct 19, 2022 at 12:07:58PM +0200, Cleo John wrote:
>>
>> Hey, because I am new to Kernel submissions I wanted to ask if there is a way for me to see / track how far this commit has gone in the pipeline of commits?
>
> https://patchwork.kernel.org/project/linux-riscv/patch/20221010182848.GA28029@watet-ms7b87/
>
> IIRC you sent the patch during the merge window, so it wouldn't be
> applied for v6.1-rc1. You'll get an email from the patchwork-bot when it
> gets applied.
Yep, this is one of the more confusing parts of the Linux development
process for new folks (or at least was for me when I was new): you send
a patch and it's not super clear what's going to happen to it for a
while. The merge window is generally a pretty hectic time, so stuff
like this that's not fixing a bug or adding some frameware that other
patches depend on can kind of get lost in the shuffle.
I always feel kind of bad for folks about that, but patchwork should
help some here as at least we can get the smaller stuff called out.
This is on for-next, thanks!
Powered by blists - more mailing lists