From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Reshma Pattan <reshma.pattan@intel.com>,
Maryam Tahhan <maryam.tahhan@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Nicolas Chautru <nicolas.chautru@intel.com>,
Olivier Matz <olivier.matz@6wind.com>,
Declan Doherty <declan.doherty@intel.com>,
Ciara Power <ciara.power@intel.com>,
Jerin Jacob <jerinj@marvell.com>,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
Wisam Jaddo <wisamm@nvidia.com>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
Ori Kam <orika@nvidia.com>,
Bernard Iremonger <bernard.iremonger@intel.com>,
Ashish Gupta <ashish.gupta@marvell.com>,
Fiona Trahe <fiona.trahe@intel.com>,
Ankur Dwivedi <adwivedi@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Tejasree Kondoj <ktejasree@marvell.com>,
Fan Zhang <roy.fan.zhang@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
John Griffin <john.griffin@intel.com>,
Deepak Kumar Jain <deepak.k.jain@intel.com>,
Qiming Yang <qiming.yang@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH] meson.build: replace tabs with spaces
Date: Tue, 2 Nov 2021 16:19:14 +0000 [thread overview]
Message-ID: <YYFlAli4GdaXvuTx@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20211102155055.214735-1-stephen@networkplumber.org>
On Tue, Nov 02, 2021 at 08:50:55AM -0700, Stephen Hemminger wrote:
> Per the meson recommendation the meson.build file
> should be indented with spaces not tabs.
> This patch is semi-automatically generated by running
> all the meson.build files through expand command.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
> Note: if users (like me) just editconfig setup in their
> favorite editor, this would not be a problem.
>
> Also, shouldn't checkpatch be made smarter to catch this?
>
> app/pdump/meson.build | 6 +--
> app/proc-info/meson.build | 6 +--
> app/test-acl/meson.build | 6 +--
> app/test-bbdev/meson.build | 8 ++--
> app/test-cmdline/meson.build | 6 +--
> app/test-compress-perf/meson.build | 6 +--
> app/test-crypto-perf/meson.build | 6 +--
> app/test-eventdev/meson.build | 6 +--
> app/test-fib/meson.build | 6 +--
> app/test-flow-perf/meson.build | 6 +--
> app/test-pipeline/meson.build | 6 +--
> app/test-regex/meson.build | 6 +--
> app/test-sad/meson.build | 6 +--
> app/test/meson.build | 6 +--
> config/meson.build | 60 +++++++++++++--------------
> drivers/compress/octeontx/meson.build | 6 +--
> drivers/crypto/cnxk/meson.build | 6 +--
> drivers/crypto/ipsec_mb/meson.build | 38 ++++++++---------
> drivers/crypto/qat/meson.build | 2 +-
> drivers/net/ice/meson.build | 2 +-
> 20 files changed, 100 insertions(+), 100 deletions(-)
>
Yes, this should be caught automatically, and David M. has already proposed
a patch to automatically check for this [1].
For your patch specifically, most of the tabs need to be replaced by
4-chars rather than 8-chars of space. The last indent (drivers/net/ice) is
the one exception, I believe, and requires an 8-space indent.
Regards,
/Bruce
[1] http://patches.dpdk.org/project/dpdk/patch/20211022205531.9966-1-david.marchand@redhat.com/
prev parent reply other threads:[~2021-11-02 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 15:50 Stephen Hemminger
2021-11-02 16:19 ` Bruce Richardson [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=YYFlAli4GdaXvuTx@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=adwivedi@marvell.com \
--cc=anoobj@marvell.com \
--cc=ashish.gupta@marvell.com \
--cc=bernard.iremonger@intel.com \
--cc=ciara.power@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=declan.doherty@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=jerinj@marvell.com \
--cc=john.griffin@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=ktejasree@marvell.com \
--cc=maryam.tahhan@intel.com \
--cc=nicolas.chautru@intel.com \
--cc=olivier.matz@6wind.com \
--cc=orika@nvidia.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=reshma.pattan@intel.com \
--cc=roy.fan.zhang@intel.com \
--cc=stephen@networkplumber.org \
--cc=vladimir.medvedkin@intel.com \
--cc=wisamm@nvidia.com \
/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).