From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net,
patches@kernelci.org, ben.hutchings@codethink.co.uk,
stable@vger.kernel.org, John Stultz <john.stultz@linaro.org>
Subject: Re: [PATCH 4.13 0/2] 4.13.7-stable review
Date: Fri, 13 Oct 2017 07:41:09 +0200 [thread overview]
Message-ID: <20171013054109.GA21174@kroah.com> (raw)
In-Reply-To: <e5fa0d68-8715-9287-4e11-a9fe4e86daa8@osg.samsung.com>
On Thu, Oct 12, 2017 at 05:45:01PM -0600, Shuah Khan wrote:
> On 10/12/2017 03:26 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.13.7 release.
> > There are 2 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Sat Oct 14 21:25:27 UTC 2017.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.13.7-rc1.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.13.y
> > and the diffstat can be found below.
> >
>
> Compiled and booted on my test system. No dmesg regressions.
> kselftest run regression since 4.13.6
>
> selftests: posix_timers
>
> selftests: raw_skew
> ========================================
> not ok 1..7 selftests: raw_skew [FAIL]
>
> No idea why yet. cc'ing John Stultz to see if he has any ideas.
That's odd, given the small number of patches here...
thanks for testing.
greg k-h
next prev parent reply other threads:[~2017-10-13 5:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 21:26 [PATCH 4.13 0/2] 4.13.7-stable review Greg Kroah-Hartman
2017-10-12 21:26 ` [PATCH 4.13 1/2] watchdog: Revert "iTCO_wdt: all versions count down twice" Greg Kroah-Hartman
2017-10-12 21:26 ` [PATCH 4.13 2/2] waitid(): Add missing access_ok() checks Greg Kroah-Hartman
2017-10-13 23:55 ` David Daney
2017-10-12 23:45 ` [PATCH 4.13 0/2] 4.13.7-stable review Shuah Khan
2017-10-13 0:09 ` John Stultz
2017-10-13 14:05 ` Shuah Khan
2017-10-13 15:12 ` Shuah Khan
2017-10-13 17:00 ` John Stultz
2017-10-13 5:41 ` Greg Kroah-Hartman [this message]
2017-10-13 12:41 ` Guenter Roeck
2017-10-13 12:54 ` Greg Kroah-Hartman
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=20171013054109.GA21174@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=ben.hutchings@codethink.co.uk \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=patches@kernelci.org \
--cc=shuahkh@osg.samsung.com \
--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