From: Oscar Carter <oscar.carter@gmx.com>
To: kernelnewbies@kernelnewbies.org
Cc: Oscar Carter <oscar.carter@gmx.com>, Kees Cook <keescook@chromium.org>
Subject: Advice about the linux kernel development process
Date: Sat, 20 Jun 2020 16:39:15 +0200 [thread overview]
Message-ID: <20200620143915.GB4330@ubuntu> (raw)
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/
Thanks in advance
Oscar Carter
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2020-06-21 23:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 14:39 Oscar Carter [this message]
2020-06-22 8:07 ` Advice about the linux kernel development process Greg KH
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=20200620143915.GB4330@ubuntu \
--to=oscar.carter@gmx.com \
--cc=keescook@chromium.org \
--cc=kernelnewbies@kernelnewbies.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).