public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH] IPv4 multicast distribution support.
Date: Tue, 17 Jan 2017 20:11:13 +0100	[thread overview]
Message-ID: <20170117191113.GI5514@otheros> (raw)
In-Reply-To: <1560076.ER48KEDWps@bentobox>

On Tue, Jan 17, 2017 at 05:54:57PM +0100, Sven Eckelmann wrote:
> > I did download the kernel source, but when I try to run the script it
> > either tells me that I don't have a valid kernel tree (when using the
> > sources for my Xubuntu kernel) or that the file I'm trying to scan
> > isn't part of the tree (when using the latest from kernel.org).  I've
> > never used that tool in the past - can you send me a usage example for
> > scanning a file in the alfred tree?
> 
> Just did this from my linux-next.git checkout:
> 
>     ./scripts/checkpatch.pl --strict --ignore=LONG_LINE_STRING \
>       --ignore=LONG_LINE --ignore=LONG_LINE_COMMENT \
>       --ignore=FSF_MAILING_ADDRESS \
>       -f ../alfred/main.c
> 
> or:
> 
>     ./scripts/checkpatch.pl --strict --ignore=LONG_LINE_STRING \
>       --ignore=LONG_LINE --ignore=LONG_LINE_COMMENT \
>       --ignore=FSF_MAILING_ADDRESS \
>       ../alfred/0001-IPv4-multicast-distribution-support.patch

Not 100% sure whether it's needed, but if you still have issues
try to at least call "make scripts" (or even "make prepare") in the
kernel source directory first.

Also, maybe simply use the vanilla tree from Torvalds with a
  $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

Should have a more up-to-date checkpatch.pl than the Ubuntu source
directory anyway.

  reply	other threads:[~2017-01-17 19:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 19:49 [B.A.T.M.A.N.] [PATCH] IPv4 multicast distribution support Jonathan Haws
2017-01-16 19:52 ` Jonathan Haws
2017-01-17  7:44 ` Sven Eckelmann
2017-01-17 15:39   ` Jonathan Haws
2017-01-17 16:54     ` Sven Eckelmann
2017-01-17 19:11       ` Linus Lüssing [this message]
2017-01-18  5:12       ` Jonathan Haws
2017-01-18  8:11         ` Sven Eckelmann
2017-01-17 19:30 ` Linus Lüssing
2017-01-18  5:06   ` Jonathan Haws

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=20170117191113.GI5514@otheros \
    --to=linus.luessing@c0d3.blue \
    --cc=b.a.t.m.a.n@lists.open-mesh.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