From: Ratheesh Kannoth <rkannoth@marvell.com>
To: Michal Kubiak <michal.kubiak@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sunil Kovvuri Goutham <sgoutham@marvell.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
Subbaraya Sundeep Bhatta <sbhatta@marvell.com>,
Geethasowjanya Akula <gakula@marvell.com>,
Srujana Challa <schalla@marvell.com>,
Hariprasad Kelam <hkelam@marvell.com>
Subject: RE: Re: [PATCH net] octeontx2-af: Promisc enable/disable through mbox
Date: Thu, 6 Jul 2023 03:18:55 +0000 [thread overview]
Message-ID: <MWHPR1801MB19180605C58796644F1501E4D32CA@MWHPR1801MB1918.namprd18.prod.outlook.com> (raw)
In-Reply-To: <ZKVxQ2HtG+GtumCj@localhost.localdomain>
> From: Michal Kubiak <michal.kubiak@intel.com>
> Sent: Wednesday, July 5, 2023 7:04 PM
> Subject: [EXT] Re: [PATCH net] octeontx2-af: Promisc enable/disable through
> mbox
> Please follow the Patchwork report.
> There are several lines exceeding 80 characters.
I cloned https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git and ./scripts/checkpatch.pl --strict --codespell --patch <patchname> is not showing these errors/warnings.
Could you please help in understanding why this restriction is removed in checkpatch.pl and kept in patchwork script ?.
Is it mandatory to fix these ? ASFAIK, 80 lines restriction is old one when screen size were small.
-Ratheesh
next prev parent reply other threads:[~2023-07-06 3:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 3:38 [PATCH net] octeontx2-af: Promisc enable/disable through mbox Ratheesh Kannoth
2023-07-05 13:33 ` Michal Kubiak
2023-07-06 3:18 ` Ratheesh Kannoth [this message]
2023-07-06 3:26 ` Jakub Kicinski
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=MWHPR1801MB19180605C58796644F1501E4D32CA@MWHPR1801MB1918.namprd18.prod.outlook.com \
--to=rkannoth@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.kubiak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=schalla@marvell.com \
--cc=sgoutham@marvell.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).