From: Al Viro <viro@ZenIV.linux.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [PATCH -next, RESEND] av32: Make sure _TIF_BREAKPOINT is defined
Date: Wed, 19 Sep 2012 03:48:38 +0100 [thread overview]
Message-ID: <20120919024838.GX13973@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1347992361-11510-1-git-send-email-geert@linux-m68k.org>
On Tue, Sep 18, 2012 at 08:19:21PM +0200, Geert Uytterhoeven wrote:
> Still not fixed after almost 4 months...
Gyah... I really need to trim that pile of internal branches; the fixed
commit had not been cherry-picked into for-next. My apologies ;-/
prev parent reply other threads:[~2012-09-19 2:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 18:19 [PATCH -next, RESEND] av32: Make sure _TIF_BREAKPOINT is defined Geert Uytterhoeven
2012-09-19 2:48 ` Al Viro [this message]
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=20120919024838.GX13973@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 \
/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).