Message-ID: <4FE02155.2010505@monstr.eu>
Date: Tue, 19 Jun 2012 08:51:01 +0200
From: Michal Simek <monstr@monstr.eu>
Reply-To: monstr@monstr.eu
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Al Viro <viro@zeniv.linux.org.uk>
CC: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org,
        LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jun 4
References: <20120604154053.31c23de0a68defd4a9f773fc@canb.auug.org.au>
In-Reply-To: <20120604154053.31c23de0a68defd4a9f773fc@canb.auug.org.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1114
Lines: 34

On 06/04/2012 07:40 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20120601:
>
> New tree: leds

Haven't tracked which branch contains it but there are two new patches
for Microblaze where at least one is wrong (compilation failure).
(Firstly merged Jun 4).
Based on that I think that these changes are not even tested on hw.

microblaze: fix the horror with restarts of sigreturn()
microblaze: fix handling of multiple pending signals

Al: Can you please give me some information about?
They should definitely go through my tree and has to be tested.
Please remove them from your branch which is merged to linux-next and send them as standard patches
to LKML and CC me.

Thanks,
Michal


-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/