From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net,
shuah.kh@samsung.com, stable@vger.kernel.org
Subject: Re: [PATCH 3.10 00/11] 3.10.88-stable review
Date: Sat, 12 Sep 2015 08:55:45 -0700 [thread overview]
Message-ID: <20150912155545.GG29944@kroah.com> (raw)
In-Reply-To: <20150912072603.GA28881@sudip-pc>
On Sat, Sep 12, 2015 at 12:56:03PM +0530, Sudip Mukherjee wrote:
> On Fri, Sep 11, 2015 at 03:48:59PM -0700, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.10.88 release.
> > There are 11 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 Sun Sep 13 22:45:08 UTC 2015.
> > Anything received after that time might be too late.
> Compiled and booted on x86_32. No errors in dmesg.
>
> cross_compiled with allmodconfig:
>
> i386 - pass
> x86_64 - pass
> alphacheck - pass
> arm - pass
> cris - failed
Is this expected?
> m68k - pass
> mips - pass
> powerpc - pass
> s390 - failed
Is this expected?
> sparc - pass
> sparc64 - pass
> tile - failed
> tilegx - failed
> xtensa - failed
Are these all new failures?
thanks,
greg k-h
next prev parent reply other threads:[~2015-09-12 15:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 22:48 [PATCH 3.10 00/11] 3.10.88-stable review Greg Kroah-Hartman
2015-09-11 22:49 ` [PATCH 3.10 01/11] ipc,sem: fix use after free on IPC_RMID after a task using same semaphore set exits Greg Kroah-Hartman
2015-09-11 22:49 ` [PATCH 3.10 02/11] ipc/sem.c: update/correct memory barriers Greg Kroah-Hartman
2015-09-11 22:49 ` [PATCH 3.10 03/11] mm/hwpoison: fix page refcount of unknown non LRU page Greg Kroah-Hartman
2015-09-11 22:49 ` [PATCH 3.10 04/11] perf: Fix fasync handling on inherited events Greg Kroah-Hartman
2015-09-11 22:49 ` [PATCH 3.10 05/11] dm thin metadata: delete btrees when releasing metadata snapshot Greg Kroah-Hartman
2015-09-11 22:49 ` [PATCH 3.10 06/11] localmodconfig: Use Kbuild files too Greg Kroah-Hartman
2015-09-11 22:49 ` [PATCH 3.10 07/11] EDAC, ppc4xx: Access mci->csrows array elements properly Greg Kroah-Hartman
2015-09-11 22:49 ` [PATCH 3.10 08/11] drm/radeon: add new OLAND pci id Greg Kroah-Hartman
2015-09-11 22:49 ` [PATCH 3.10 09/11] libfc: Fix fc_fcp_cleanup_each_cmd() Greg Kroah-Hartman
2015-09-11 22:49 ` [PATCH 3.10 10/11] crypto: caam - fix memory corruption in ahash_final_ctx Greg Kroah-Hartman
2015-09-11 22:49 ` [PATCH 3.10 11/11] arm64/mm: Remove hack in mmap randomize layout Greg Kroah-Hartman
2015-09-12 1:07 ` [PATCH 3.10 00/11] 3.10.88-stable review Shuah Khan
2015-09-12 4:21 ` Guenter Roeck
2015-09-12 7:26 ` Sudip Mukherjee
2015-09-12 15:55 ` Greg Kroah-Hartman [this message]
2015-09-12 16:22 ` Max Filippov
2015-09-12 17:36 ` Sudip Mukherjee
2015-09-12 17:51 ` Guenter Roeck
2015-09-12 18:12 ` Sudip Mukherjee
2015-09-14 9:01 ` Sudip Mukherjee
2015-09-21 1:43 ` Greg Kroah-Hartman
2015-09-12 17:41 ` Sudip Mukherjee
2015-09-12 17:41 ` Guenter Roeck
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=20150912155545.GG29944@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=shuah.kh@samsung.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--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.