From: Michal Simek <monstr@monstr.eu>
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
Date: Tue, 19 Jun 2012 08:51:01 +0200 [thread overview]
Message-ID: <4FE02155.2010505@monstr.eu> (raw)
In-Reply-To: <20120604154053.31c23de0a68defd4a9f773fc@canb.auug.org.au>
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
next prev parent reply other threads:[~2012-06-19 6:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 5:40 linux-next: Tree for Jun 4 Stephen Rothwell
2012-06-19 6:51 ` Michal Simek [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-04 7:41 Stephen Rothwell
2014-06-04 8:29 Stephen Rothwell
2015-06-04 13:15 Stephen Rothwell
2018-06-04 11:59 Stephen Rothwell
2019-06-04 6:09 Stephen Rothwell
2020-06-04 7:08 Stephen Rothwell
2021-06-04 8:13 Stephen Rothwell
2024-06-04 3:35 Stephen Rothwell
2025-06-04 4:02 Stephen Rothwell
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=4FE02155.2010505@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).