From: Al Viro <viro@ZenIV.linux.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Russell King <rmk@arm.linux.org.uk>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Will Deacon <will.deacon@arm.com>
Subject: Re: linux-next: manual merge of the signal tree with the arm-current tree
Date: Sun, 15 Jul 2012 13:04:57 +0100 [thread overview]
Message-ID: <20120715120457.GJ31729@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAMuHMdXP_rjwPhfTwcY+Jf3+Dq=AkWtMZvUUibCQ9D=c60_j5Q@mail.gmail.com>
On Sun, Jul 15, 2012 at 01:47:59PM +0200, Geert Uytterhoeven wrote:
> Hi Al,
>
> On Sun, Jul 15, 2012 at 1:27 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> > On Thu, Jul 05, 2012 at 08:52:04AM +0100, Russell King wrote:
> >> Will has concerns with Al's proposed fixes for the signal handling.
> >
> > Could you please resend whatever concerns those had been my way?
> > The last I've seen from Will had been about the stuff in mainline,
> > not in -next; I might have missed something quite easily, though -
> > net.access had been really lousy lately and piles in l-k mbox... ouch.
>
> Speaking about -next, there's still this fix for an avr32 regression:
Yeah, grabbed it. Will be in the next rebase (hopefully in a few hours).
next prev parent reply other threads:[~2012-07-15 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 7:35 linux-next: manual merge of the signal tree with the arm-current tree Stephen Rothwell
2012-07-05 7:52 ` Russell King
2012-07-06 1:29 ` Stephen Rothwell
2012-07-15 11:27 ` Al Viro
2012-07-15 11:47 ` Geert Uytterhoeven
2012-07-15 12:04 ` Al Viro [this message]
2012-08-04 19:19 ` Geert Uytterhoeven
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=20120715120457.GJ31729@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=sfr@canb.auug.org.au \
--cc=will.deacon@arm.com \
/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).