From: Willy Tarreau <w@1wt.eu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Stable queue is caught up on for 3.10, 3.14, 4.1, and 4.2-stable kernels
Date: Sun, 18 Oct 2015 07:56:06 +0200 [thread overview]
Message-ID: <20151018055606.GA31884@1wt.eu> (raw)
In-Reply-To: <20151018020952.GA6056@kroah.com>
Hi Greg,
On Sat, Oct 17, 2015 at 07:09:52PM -0700, Greg KH wrote:
> Hi all,
>
> I've finally caught up on all pending patches for the above mentioned
> stable kernels that have either hit Linus's tree with a stable@ or
> fixes: marking, or have been emailed to the stable@ list requesting to
> be included.
Impressed :-)
I'm seeing that each series ends with patch (N-1)/N, so I think something
changed in your scripts, either N is wrong in which case we can ignore
this, or the last patch of each series was not sent.
Could you please double-check ?
Thanks,
Willy
next prev parent reply other threads:[~2015-10-18 5:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 2:09 Stable queue is caught up on for 3.10, 3.14, 4.1, and 4.2-stable kernels Greg KH
2015-10-18 5:56 ` Willy Tarreau [this message]
2015-10-18 6:02 ` Greg KH
2015-10-18 6:05 ` Willy Tarreau
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=20151018055606.GA31884@1wt.eu \
--to=w@1wt.eu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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