From: Conor Dooley <conor.dooley@microchip.com>
To: Cleo John <waterdev@galaxycrow.de>
Cc: Conor Dooley <conor@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <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: Wed, 19 Oct 2022 11:20:44 +0100 [thread overview]
Message-ID: <Y0/PfL5SWNw8HCLr@wendy> (raw)
In-Reply-To: <4763163.GXAFRqVoOG@watet-ms7b87>
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.
HTH,
Conor.
_______________________________________________
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.dooley@microchip.com>
To: Cleo John <waterdev@galaxycrow.de>
Cc: Conor Dooley <conor@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <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: Wed, 19 Oct 2022 11:20:44 +0100 [thread overview]
Message-ID: <Y0/PfL5SWNw8HCLr@wendy> (raw)
In-Reply-To: <4763163.GXAFRqVoOG@watet-ms7b87>
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.
HTH,
Conor.
next prev parent reply other threads:[~2022-10-19 10:21 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 [this message]
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
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=Y0/PfL5SWNw8HCLr@wendy \
--to=conor.dooley@microchip.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--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.