DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Cc: <thomas@monjalon.net>, <Honnappa.Nagarahalli@arm.com>,
	<jspewock@iol.unh.edu>, <probb@iol.unh.edu>,
	<stephen@networkplumber.org>, <dev@dpdk.org>
Subject: Re: [PATCH v2 2/2] dts: reformat to 100 line length
Date: Thu, 28 Sep 2023 09:42:36 +0100	[thread overview]
Message-ID: <ZRU8fEpDeNI5KSww@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CAOb5WZZQugCH81jXwznxN9zQ2oiFpiiEcRbDe_2X4bgZ=zaNRg@mail.gmail.com>

On Thu, Sep 28, 2023 at 09:33:55AM +0200, Juraj Linkeš wrote:
> On Wed, Sep 27, 2023 at 10:08 AM Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> >
> > On Tue, Sep 26, 2023 at 02:10:13PM +0200, Juraj Linkeš wrote:
> > > Reformat to 100 from the previous 88 to unify with C recommendations.
> > >
> > > Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
> >
> > Generally for something like this we wouldn't reformat the existing code,
> > because it confuses the git history e.g. for those looking for "fixlines"
> > for bug fixes. However, given that DTS is so new in the repo, it's probably
> > ok and worthwhile doing.
> >
> > Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> 
> Thanks for pointing this out, Bruce, I'll keep it in mind for the
> future. For now, it's kinda necessary we do this because our reformat
> tool, Black, reformats the whole codebase so I think the pros outweigh
> the cons.
>
Agreed 

  reply	other threads:[~2023-09-28  8:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 13:29 [PATCH v1 0/2] python gitignore and " Juraj Linkeš
2022-11-03 13:29 ` [PATCH v1 1/2] git: ignore standard python files Juraj Linkeš
2022-11-04  9:16   ` Juraj Linkeš
2022-11-04  9:26   ` Bruce Richardson
2023-07-16 18:11   ` [PATCH] doc: fix description of runtime directories Stephen Hemminger
2023-07-20  3:26     ` Thomas Monjalon
2022-11-03 13:29 ` [PATCH v1 2/2] doc: increase python max line to 88 Juraj Linkeš
2022-11-04  9:16   ` Juraj Linkeš
2022-11-04  9:28     ` Bruce Richardson
2022-11-04 16:57     ` Stephen Hemminger
2022-11-10  9:15       ` Juraj Linkeš
2022-11-10 16:27         ` Stephen Hemminger
2023-09-26 12:10   ` [PATCH v2 1/2] doc: increase python max line length to 100 Juraj Linkeš
2023-09-26 12:10     ` [PATCH v2 2/2] dts: reformat to 100 line length Juraj Linkeš
2023-09-26 21:52       ` Jeremy Spewock
2023-09-28  7:27         ` Juraj Linkeš
2023-09-27  8:08       ` Bruce Richardson
2023-09-28  7:33         ` Juraj Linkeš
2023-09-28  8:42           ` Bruce Richardson [this message]
2023-09-26 13:00     ` [PATCH v2 1/2] doc: increase python max line length to 100 Bruce Richardson
2023-09-28 12:18     ` [PATCH v3 " Juraj Linkeš
2023-09-28 12:18       ` [PATCH v3 2/2] dts: reformat to 100 line length Juraj Linkeš
2023-09-29 16:53         ` Jeremy Spewock
2023-10-13  7:58         ` [PATCH v4 1/2] doc: increase python max line length to 100 Juraj Linkeš
2023-10-13  7:58           ` [PATCH v4 2/2] dts: reformat to 100 line length Juraj Linkeš
2023-10-16  6:45             ` [PATCH v5 1/2] doc: increase python max line length to 100 Juraj Linkeš
2023-10-16  6:45               ` [PATCH v5 2/2] dts: reformat to 100 line length Juraj Linkeš
2023-11-20 12:36                 ` [PATCH v6 1/2] doc: increase python max line length to 100 Juraj Linkeš
2023-11-20 12:36                   ` [PATCH v6 2/2] dts: reformat to 100 line length Juraj Linkeš
2023-11-20 16:50                     ` Thomas Monjalon
2023-11-21  9:27                       ` Juraj Linkeš
2023-10-13 16:09           ` [PATCH v4 1/2] doc: increase python max line length to 100 Stephen Hemminger
2023-10-16  6:44             ` Juraj Linkeš
2023-10-12 12:52       ` [PATCH v3 " Paul Szczepanek
2023-10-13  7:56         ` Juraj Linkeš
2022-11-04  9:15 ` [PATCH v1 0/2] python gitignore and line length Juraj Linkeš

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=ZRU8fEpDeNI5KSww@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=dev@dpdk.org \
    --cc=jspewock@iol.unh.edu \
    --cc=juraj.linkes@pantheon.tech \
    --cc=probb@iol.unh.edu \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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).