From: Al Viro <viro@ZenIV•linux.org.uk>
To: Heiko Carstens <heiko.carstens@de•ibm.com>
Cc: linux-next@vger•kernel.org
Subject: Re: [PATCH -next] s390/signal: fix compile error
Date: Fri, 1 Jun 2012 08:34:34 +0100 [thread overview]
Message-ID: <20120601073433.GH30000@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20120601071704.GA3535@osiris.boeblingen.de.ibm.com>
On Fri, Jun 01, 2012 at 09:17:05AM +0200, Heiko Carstens wrote:
> Hi Al,
>
> could you please add/merge the patch below which fixes a simple compile
> error in linux-next caused by your signal work?
Already there. I really need to do something about the workflow on
cross-builds - that's not the first time fixes get lost and not
moved from tree on a build box to the devel one ;-/
prev parent reply other threads:[~2012-06-01 7:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 7:17 [PATCH -next] s390/signal: fix compile error Heiko Carstens
2012-06-01 7:34 ` 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=20120601073433.GH30000@ZenIV.linux.org.uk \
--to=viro@zeniv$(echo .)linux.org.uk \
--cc=heiko.carstens@de$(echo .)ibm.com \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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