From: ydroneaud@opteya.com (Yann Droneaud)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Problem facing while running checkpatch.pl on linux-next tree
Date: Sun, 27 Jul 2014 12:03:58 +0200 [thread overview]
Message-ID: <1406455438.4911.1.camel@localhost.localdomain> (raw)
In-Reply-To: <CALeaES3WKfQhSUXHNiw3UxwaJbu6e2Xr4w9gV108+4r4b=AonQ@mail.gmail.com>
Hi,
Le dimanche 27 juillet 2014 ? 14:30 +0530, Rahul Garg a ?crit :
> I am trying to run checkpatch.pl on linux-next tree's staging folder.
> But whatever sub directory, I try to run it on. It is giving me the
> same error for all the files :
>
> ERROR: Does not appear to be a unified-diff format patch
>
> I thought that it might be a problem with my git. So I clone the git tree again.
>
> So can anyone help me, what am I missing ?
>
If it's not a patch, you have to use -f flag to check a plain source
file.
Regards.
--
Yann Droneaud
OPTEYA
next prev parent reply other threads:[~2014-07-27 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 9:00 Problem facing while running checkpatch.pl on linux-next tree Rahul Garg
2014-07-27 9:47 ` Sudip Mukherjee
2014-07-27 10:03 ` Yann Droneaud [this message]
2014-07-27 18:08 ` anish singh
2014-12-25 10:11 ` Jitendra kumar Khasdev
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=1406455438.4911.1.camel@localhost.localdomain \
--to=ydroneaud@opteya.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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).