linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Glauber <jang@linux.vnet.ibm.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
	linux-next@vger.kernel.org,
	Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: linux-next / s390 crypto breakage
Date: Thu, 03 Sep 2009 15:52:22 +0000	[thread overview]
Message-ID: <1251993142.7382.8.camel@bender> (raw)
In-Reply-To: <20090902220447.GA17101@gondor.apana.org.au>

On Thu, 2009-09-03 at 08:04 +1000, Herbert Xu wrote:
> On Wed, Sep 02, 2009 at 05:57:25PM +0000, Jan Glauber wrote:
> > That patch should fix the warnings.
> 
> Thanks, but where is the sign-off :)

Oops. I need a script for that...

Signed-off-by: Jan Glauber <jang@linux.vnet.ibm.com>

  reply	other threads:[~2009-09-03 13:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 11:35 linux-next / s390 crypto breakage Heiko Carstens
2009-09-02 17:57 ` Jan Glauber
2009-09-02 22:04   ` Herbert Xu
2009-09-03 15:52     ` Jan Glauber [this message]
2009-09-05  6:28       ` Herbert Xu

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=1251993142.7382.8.camel@bender \
    --to=jang@linux.vnet.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-next@vger.kernel.org \
    --cc=schwidefsky@de.ibm.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).