From: Rusty Russell <rusty@rustcorp.com.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: linux-next: import of rr series failed
Date: Wed, 19 Oct 2011 10:21:48 +1030 [thread overview]
Message-ID: <87botdc0yz.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20111014103638.accaae53bac0e74da3c787bd@canb.auug.org.au>
On Fri, 14 Oct 2011 10:36:38 +1100, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
Non-text part: multipart/signed
> Hi Rusty,
>
> Importing the rr series today I got this error:
>
> $ git am ../quilt/rr/virtio:dont_add_config_to_list_for_per_vq_vector.patch
> Patch format detection failed.
>
> I added a From line to the top using the address from the first SOB line.
Weird, don't know how that slipped through my checking script :(
Fixed up now, thanks.
Rusty.
prev parent reply other threads:[~2011-10-19 3:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 23:36 linux-next: import of rr series failed Stephen Rothwell
2011-10-18 23:51 ` Rusty Russell [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=87botdc0yz.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).