From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: import of the kernel-doc tree failed
Date: Thu, 15 Sep 2011 09:10:25 -0700 [thread overview]
Message-ID: <4E722371.2060908@xenotime.net> (raw)
In-Reply-To: <20110915111301.a4227f9ca0d1f448d54050ae@canb.auug.org.au>
On 09/14/11 18:13, Stephen Rothwell wrote:
> Hi Randy,
>
> Importing the kernel-doc tree today produced this error:
>
> $ git am ../quilt/kernel-doc/docum-leds-class-fix-typo.patch
> Patch format detection failed.
>
> I just had to replace the tab in the From: line with a space.
I fixed my version of the patch.
Thanks.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2011-09-15 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 1:13 linux-next: import of the kernel-doc tree failed Stephen Rothwell
2011-09-15 16:10 ` Randy Dunlap [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=4E722371.2060908@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--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).