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,
Denis Kirjanov <kda@linux-powerpc.org>
Subject: Re: [PATCH 3.16 0/4] 3.16.73-rc1 review
Date: Sun, 18 Aug 2019 17:41:36 +0100 [thread overview]
Message-ID: <a1775491e3dffb60afce950a28807f4049e3bf1c.camel@decadent.org.uk> (raw)
In-Reply-To: <9bfbe161-70c5-d969-98e9-b94c911f09f6@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
On Sat, 2019-08-17 at 04:19 -0700, Guenter Roeck wrote:
> On 8/17/19 3:35 AM, Ben Hutchings wrote:
> > This is the start of the stable review cycle for the 3.16.73 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 Mon Aug 19 20:00:00 UTC 2019.
> > Anything received after that time might be too late.
> >
> Build results:
> total: 136 pass: 136 fail: 0
> Qemu test results:
> total: 229 pass: 229 fail: 0
Thanks for testing,
Ben.
--
Ben Hutchings
Larkinson's Law: All laws are basically false.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-08-18 16:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-17 10:35 Ben Hutchings
2019-08-17 10:35 ` [PATCH 3.16 2/4] ext4: brelse all indirect buffer in ext4_ind_remove_space() Ben Hutchings
2019-08-17 10:35 ` [PATCH 3.16 1/4] tcp: Clear sk_send_head after purging the write queue Ben Hutchings
2019-08-17 10:35 ` [PATCH 3.16 3/4] ext4: cleanup bh release code in ext4_ind_remove_space() Ben Hutchings
2019-08-17 10:35 ` [PATCH 3.16 4/4] siphash: implement HalfSipHash1-3 for hash tables Ben Hutchings
2019-08-17 11:19 ` [PATCH 3.16 0/4] 3.16.73-rc1 review Guenter Roeck
2019-08-18 16:41 ` 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=a1775491e3dffb60afce950a28807f4049e3bf1c.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=akpm@linux-foundation.org \
--cc=kda@linux-powerpc.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®