All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Kevin Cernekee <cernekee@gmail.com>
Cc: tglx@linutronix.de, gnomes@lxorguk.ukuu.org.uk,
	computersforpeace@gmail.com, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, corbet@lwn.net,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC 2/4] Documentation/SubmitChecklist: Remind submitters to check the merge window
Date: Mon, 15 Dec 2014 11:17:57 +0100	[thread overview]
Message-ID: <20141215101757.GC6444@pd.tnic> (raw)
In-Reply-To: <1418623790-28429-3-git-send-email-cernekee@gmail.com>

On Sun, Dec 14, 2014 at 10:09:48PM -0800, Kevin Cernekee wrote:
> Currently the checklist does not provide an indication of appropriate
> times to send patches; add a brief note on the topic.
> 
> Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
> ---
>  Documentation/SubmitChecklist | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/Documentation/SubmitChecklist b/Documentation/SubmitChecklist
> index 2b7e32d..8b23f9c 100644
> --- a/Documentation/SubmitChecklist
> +++ b/Documentation/SubmitChecklist
> @@ -107,3 +107,8 @@ kernel patches.
>      CONFIG_SMP, CONFIG_SYSFS, CONFIG_PROC_FS, CONFIG_INPUT, CONFIG_PCI,
>      CONFIG_BLOCK, CONFIG_PM, CONFIG_MAGIC_SYSRQ,
>      CONFIG_NET, CONFIG_INET=n (but latter with CONFIG_NET=y)
> +
> +27: For patches which are not urgent fixes for bugs in the current tree,
> +    double-check https://www.kernel.org/ to make sure the merge window is
> +    CLOSED ("mainline:" showing an -rc kernel) before sending.  For more
> +    information on the release cycle, see Documentation/development-process/.

Acked-by: Borislav Petkov <bp@suse.de>

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2014-12-15 10:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15  6:09 [RFC 0/4] Stop maintainer abuse Kevin Cernekee
2014-12-15  6:09 ` [RFC 1/4] Documentation: Change policy on sending patches during merge window Kevin Cernekee
2014-12-15  8:29   ` Christoph Hellwig
2014-12-15  6:09 ` [RFC 2/4] Documentation/SubmitChecklist: Remind submitters to check the " Kevin Cernekee
2014-12-15 10:17   ` Borislav Petkov [this message]
2014-12-16  6:48   ` Kalle Valo
2014-12-15  6:09 ` [RFC 3/4] Documentation: Add cutoff periods for patch acceptance Kevin Cernekee
2014-12-15 10:15   ` Borislav Petkov
2014-12-15 14:59   ` One Thousand Gnomes
2014-12-15 18:29     ` Linus Torvalds
2014-12-15  6:09 ` [RFC 4/4] Documentation: Provide suggestions on when to repost patches Kevin Cernekee
2014-12-15 10:13   ` Borislav Petkov
2014-12-16 18:09 ` [RFC 0/4] Stop maintainer abuse Jonathan Corbet
2014-12-16 20:35   ` Theodore Ts'o
2014-12-16 22:19   ` Kevin Cernekee
2014-12-16 22:31     ` Borislav Petkov
2014-12-17  5:14       ` Theodore Ts'o
2014-12-17  9:52         ` Borislav Petkov
2014-12-18 19:05           ` Mark Brown
2014-12-18 10:35   ` Paolo Bonzini
2014-12-18 10:42     ` Borislav Petkov
2014-12-18 10:53       ` Paolo Bonzini

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=20141215101757.GC6444@pd.tnic \
    --to=bp@alien8.de \
    --cc=akpm@linux-foundation.org \
    --cc=cernekee@gmail.com \
    --cc=computersforpeace@gmail.com \
    --cc=corbet@lwn.net \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 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.