From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
waterdev@galaxycrow.de, Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] riscv: fix styling in ucontext header
Date: Fri, 28 Oct 2022 23:42:55 +0100 [thread overview]
Message-ID: <Y1xa782WsdULPIiL@spud> (raw)
In-Reply-To: <mhng-036eff83-1a93-4e98-9810-a4abb79e55e7@palmer-ri-x1c9a>
On Fri, Oct 28, 2022 at 03:23:21PM -0700, Palmer Dabbelt wrote:
> 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
Nope, was the case for me too. Same applies to most subsystems, think
probably places like netdev are good in that regard as their review
cadence is really good.
> 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.
Yeah, hopefully patchwork helps. If we keep on top of it & over time
it'll get more useful for infrequent contributors - but for first time
contributors I'm not sure what to do other than for people that notice
it is a first time contributor to be helpful to them?
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
waterdev@galaxycrow.de, Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] riscv: fix styling in ucontext header
Date: Fri, 28 Oct 2022 23:42:55 +0100 [thread overview]
Message-ID: <Y1xa782WsdULPIiL@spud> (raw)
In-Reply-To: <mhng-036eff83-1a93-4e98-9810-a4abb79e55e7@palmer-ri-x1c9a>
On Fri, Oct 28, 2022 at 03:23:21PM -0700, Palmer Dabbelt wrote:
> 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
Nope, was the case for me too. Same applies to most subsystems, think
probably places like netdev are good in that regard as their review
cadence is really good.
> 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.
Yeah, hopefully patchwork helps. If we keep on top of it & over time
it'll get more useful for infrequent contributors - but for first time
contributors I'm not sure what to do other than for people that notice
it is a first time contributor to be helpful to them?
next prev parent reply other threads:[~2022-10-28 22:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 18:28 [PATCH v2] riscv: fix styling in ucontext header Cleo John
2022-10-10 18:28 ` Cleo John
2022-10-10 18:50 ` Conor Dooley
2022-10-10 18:50 ` Conor Dooley
2022-10-10 19:55 ` Cleo John
2022-10-10 19:55 ` Cleo John
2022-10-10 20:41 ` Conor Dooley
2022-10-10 20:41 ` Conor Dooley
2022-10-19 10:07 ` Cleo John
2022-10-19 10:07 ` Cleo John
2022-10-19 10:20 ` Conor Dooley
2022-10-19 10:20 ` Conor Dooley
2022-10-28 22:23 ` Palmer Dabbelt
2022-10-28 22:23 ` Palmer Dabbelt
2022-10-28 22:42 ` Conor Dooley [this message]
2022-10-28 22:42 ` Conor Dooley
2022-10-28 22:23 ` Palmer Dabbelt
2022-10-28 22:23 ` Palmer Dabbelt
-- strict thread matches above, loose matches on Subject: below --
2022-10-09 13:13 Cleo John
2022-10-09 13:13 ` Cleo John
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=Y1xa782WsdULPIiL@spud \
--to=conor@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=waterdev@galaxycrow.de \
/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.