From: Al Viro <viro@ZenIV.linux.org.uk>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: fix invocation of restore_altstack
Date: Thu, 14 Feb 2013 14:26:35 +0000 [thread overview]
Message-ID: <20130214142635.GT4503@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20130214133552.GB25537@e106331-lin.cambridge.arm.com>
On Thu, Feb 14, 2013 at 01:35:52PM +0000, Mark Rutland wrote:
> Hello,
>
> I noticed the following issue while attempting to build an arm64 kernel from
> next-20130214, and it still seems to be present in signal/for-next and
> signal/arch-arm64.
>
> It looks to be a trivial typo.
Thanks; folded and pushed.
prev parent reply other threads:[~2013-02-14 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 13:35 Mark Rutland
2013-02-14 14:26 ` 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=20130214142635.GT4503@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=Catalin.Marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@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
all inboxes | Powered by JetHome®