From: Ben Hutchings <ben@decadent.org.uk>
To: Guenter Roeck <linux@roeck-us.net>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org
Subject: Re: [PATCH 3.2 0/4] 3.2.86-rc1 review
Date: Fri, 24 Feb 2017 16:31:04 +0000 [thread overview]
Message-ID: <1487953864.26310.10.camel@decadent.org.uk> (raw)
In-Reply-To: <63a3e1d4-4cdd-0302-7122-af2fba19104e@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
On Fri, 2017-02-24 at 08:18 -0800, Guenter Roeck wrote:
> On 02/24/2017 04:07 AM, Ben Hutchings wrote:
> > This is the start of the stable review cycle for the 3.2.86 release.
> > There are 4 patches in this series, which will be posted as responses
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Sun Feb 26 12:07:01 UTC 2017.
> > Anything received after that time might be too late.
> >
>
> Build results:
> total: 89 pass: 89 fail: 0
> Qemu test results:
> total: 69 pass: 69 fail: 0
>
> Details are available at http://kerneltests.org/builders.
Thanks for testing!
Ben.
--
Ben Hutchings
All the simple programs have been written, and all the good names
taken.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-02-24 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 12:07 Ben Hutchings
2017-02-24 12:07 ` [PATCH 3.2 1/4] kvm: nVMX: Allow L1 to intercept software exceptions (#BP and #OF) Ben Hutchings
2017-02-24 12:07 ` [PATCH 3.2 4/4] tcp: avoid infinite loop in tcp_splice_read() Ben Hutchings
2017-02-24 12:07 ` [PATCH 3.2 3/4] dccp: fix freeing skb too early for IPV6_RECVPKTINFO Ben Hutchings
2017-02-24 12:07 ` [PATCH 3.2 2/4] USB: serial: kl5kusb105: fix line-state error handling Ben Hutchings
2017-02-24 16:18 ` [PATCH 3.2 0/4] 3.2.86-rc1 review Guenter Roeck
2017-02-24 16:31 ` Ben Hutchings [this message]
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=1487953864.26310.10.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=stable@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®