From: Greg KH <gregkh@linuxfoundation.org>
To: outreachy-kernel@googlegroups.com
Subject: patch queue now empty
Date: Wed, 4 Nov 2015 13:01:06 -0800 [thread overview]
Message-ID: <20151104210106.GA9508@kroah.com> (raw)
Hi all,
I've now processed all patches submitted for the outreachy kernel
positions. If you have not received an email, and you had sent a patch,
please consider it lost and resend it after you have refreshed it
against my staging-testing branch and I will review it then.
If you wish to continue to do staging tree cleanup work like this,
please feel free to do so, but use the tool scripts/get_maintainer.pl to
determine the mailing list and developers to cc: on your patch. It's
not ok to send new patches to this list at this point in time, sorry.
Also remember that coding style cleanups are usually not accepted except
in a few subsystems like drivers/staging/*
thanks,
greg k-h
reply other threads:[~2015-11-04 21:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20151104210106.GA9508@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.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 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.