All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjarni Ingi Gislason <bjarniig@simnet.is>
To: David Ahern <dsahern@kernel.org>
Cc: Stephen Hemminger <stephen@networkplumber.org>, netdev@vger.kernel.org
Subject: Re: tc.8: some remarks and a patch for the manual
Date: Thu, 29 Jun 2023 16:50:31 +0000	[thread overview]
Message-ID: <ZJ22V4RxekUmretl@localhost> (raw)
In-Reply-To: <9e9d932b-79df-e67c-abeb-b50bbb81b95a@kernel.org>

On Wed, Jun 28, 2023 at 12:22:02PM -0600, David Ahern wrote:
> On 6/27/23 6:44 PM, Bjarni Ingi Gislason wrote:
> >> Running checkpatch on this patch will show these things.
> > 
> >   Here is a simplified patch based on the latest "iproute2" repository.
> > 
> >   Output from "checkpatch.pl" when run in the "git/iproute2" directory
> > with the patch:
> > 
> > Must be run from the top-level dir. of a kernel tree
> > 
> 
> Add '--root /path/to/kernel/tree' to checkpatch.pl
> 

  Thanks.

  Found the right argument for "--root".

~/src/next-linux is a link to "linux-source-6.3.7-1" (from Debian testing)

/home/bg/bin/checkpatch.pl -> /home/bg/src/next-linux/scripts/checkpatch.pl

checkpatch.pl --root ~/src/next-linux 0001-iproute2-man-man8-tc.8-some-editorial-changes-to-the-m.txt

total: 0 errors, 0 warnings, 215 lines checked

0001-iproute2-man-man8-tc.8-some-editorial-changes-to-the-m.txt has no obvious style problems and is ready for submission.

      reply	other threads:[~2023-06-29 16:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24 21:43 tc.8: some remarks and a patch for the manual Bjarni Ingi Gislason
2023-06-27 17:38 ` Stephen Hemminger
2023-06-28  0:44   ` Bjarni Ingi Gislason
2023-06-28 18:22     ` David Ahern
2023-06-29 16:50       ` Bjarni Ingi Gislason [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=ZJ22V4RxekUmretl@localhost \
    --to=bjarniig@simnet.is \
    --cc=dsahern@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.