From: Greg KH <greg@kroah.com>
To: Oscar Carter <oscar.carter@gmx.com>
Cc: Kees Cook <keescook@chromium.org>, kernelnewbies@kernelnewbies.org
Subject: Re: Advice about the linux kernel development process
Date: Mon, 22 Jun 2020 10:07:40 +0200 [thread overview]
Message-ID: <20200622080740.GB3364562@kroah.com> (raw)
In-Reply-To: <20200620143915.GB4330@ubuntu>
On Sat, Jun 20, 2020 at 04:39:15PM +0200, Oscar Carter wrote:
> Hi,
>
> I've been working in the KSPP task number 20: "Enable -Wcast-function-type
> globally" [1] but now I have some questions about the development process.
>
> I sent a v3 patch for the firewire subsystem [2] and a v5 patch series for
> the acpi/irqchip subsystems [3]. During the process I've received comments
> and suggestions about my work but now these two threads have no responses
> in three weeks.
>
> When I've send patches to the staging area if they have no responses, in a
> few days I received a mail from Greg to tell me that the specific patch had
> been applied to one of the branches of his git tree.
>
> Now, what it's the correct workflow out of the staging area? Are these
> patches in a process of been applied or have they been forgotten? Do I need
> to insist? And how?
>
> [1] https://github.com/KSPP/linux/issues/20
> [2] https://lore.kernel.org/kernel-hardening/20200530090839.7895-1-oscar.carter@gmx.com/
> [3] https://lore.kernel.org/kernel-hardening/20200530143430.5203-1-oscar.carter@gmx.com/
Each subsystem works in different ways, but almost always, after 3
weeks, you can send a nice response to your patches of "hey, any
comments on this?" if you haven't heard anything.
Note that during the 2 week merge window, developers can not take new
patches, so that sometimes does cause extra delays.
good luck!
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-06-22 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 14:39 Advice about the linux kernel development process Oscar Carter
2020-06-22 8:07 ` Greg KH [this message]
2020-06-27 11:45 ` Oscar Carter
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=20200622080740.GB3364562@kroah.com \
--to=greg@kroah.com \
--cc=keescook@chromium.org \
--cc=kernelnewbies@kernelnewbies.org \
--cc=oscar.carter@gmx.com \
/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).