From: Markus Elfring <Markus.Elfring@web.de>
To: Suman Ghosh <sumang@marvell.com>, netdev@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jerin Jacob <jerinj@marvell.com>,
Eric Dumazet <edumazet@google.com>,
Geethasowjanya Akula <gakula@marvell.com>,
Hariprasad Kelam <hkelam@marvell.com>,
Linu Cherian <lcherian@marvell.com>,
Paolo Abeni <pabeni@redhat.com>,
Subbaraya Sundeep Bhatta <sbhatta@marvell.com>,
Sunil Kovvuri Goutham <sgoutham@marvell.com>
Subject: Re: [net PATCH v2 0/7] octeontx2-af: Fix klockwork issues in AF driver
Date: Tue, 25 Jun 2024 21:50:33 +0200 [thread overview]
Message-ID: <f3514471-9978-4aad-af40-e4970827a61b@web.de> (raw)
In-Reply-To: <SJ0PR18MB52166806AA7FB13ED3DC3E39DBD52@SJ0PR18MB5216.namprd18.prod.outlook.com>
> > * Why did you not directly respond to the recurring patch review concern
> > about better summary phrases (or message subjects)?
…
> [Suman] I thought the “summery phrase” is per patch.
Summaries are obviously important parts for patch subjects.
> The cover letter is mentioning the reason for the change
I would like to read an improved overview for your change approach.
> and each patch set is adding the summery for the change.
I have got understanding difficulties for such information somehow.
> Since it is not some actual ‘fix’ I am not sure what more to add other
It seems that there is a temporary conflict according to expected explanation quality.
> than mentioning klockwork fixes.
Source code analysis tools can provide more helpful information.
Do I need to remind you for the published software documentation
around “C checkers”?
> I am not sure what more can be added for a variable initialization to zero
> or adding a NULL check.
* Common vulnerability enumeration?
* CERT reference?
> Can you suggest some?
* Please take another look at linked information sources.
* Can you get sufficient inspirations from published patches?
> > * Would you like to explain any more here which development concern categories
> > were picked up from the mentioned source code analysis tool?
>
> [Suman] Development concerns are mentioned in individual patch sets.
* Grouping?
* Outlines?
* Taxonomy?
> > * How much do you care for the grouping of logical changes into
> > consistent patch series?
>
> [Suman] I thought about it but then I was not sure
> how to add fix tags for a unified patch set.
Why did you not ask before sending another questionable patch series?
> Hence went with per file approach.
It can occasionally be helpful for change preparations.
> Do you see any problem with the approach?
Obviously, yes.
I hope that you can take several patch review issues better into account finally.
Regards,
Markus
next prev parent reply other threads:[~2024-06-25 19:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 17:33 Suman Ghosh
2024-06-25 17:33 ` [net PATCH v2 1/7] octeontx2-af: Fix klockwork issue in cgx.c Suman Ghosh
2024-06-26 1:04 ` Jakub Kicinski
2024-06-25 17:33 ` [net PATCH v2 2/7] octeontx2-af: Fix klockwork issue in mcs_rvu_if.c Suman Ghosh
2024-06-25 17:33 ` [net PATCH 2/7] octeontx2-af: Fix klockwork issues " Suman Ghosh
2024-06-25 18:37 ` Markus Elfring
2024-06-25 17:33 ` [net PATCH v2 3/7] octeontx2-af: Fixes klockwork issues in ptp.c Suman Ghosh
2024-06-25 17:33 ` [net PATCH v2 4/7] octeontx2-af: Fixes klockwork issues in rvu_cpt.c Suman Ghosh
2024-06-25 17:33 ` [net PATCH v2 5/7] octeontx2-af: Fixes klockwork issues in rvu_debugfs.c Suman Ghosh
2024-06-25 17:33 ` [net PATCH v2 6/7] octeontx2-af: Fix klockwork issue in rvu_nix.c Suman Ghosh
2024-06-25 17:33 ` [net PATCH v2 7/7] octeontx2-af: Fix klockwork issue in rvu_npc.c Suman Ghosh
2024-06-25 18:17 ` [net PATCH v2 0/7] octeontx2-af: Fix klockwork issues in AF driver Markus Elfring
[not found] ` <SJ0PR18MB52166806AA7FB13ED3DC3E39DBD52@SJ0PR18MB5216.namprd18.prod.outlook.com>
2024-06-25 19:50 ` Markus Elfring [this message]
2024-06-26 1:04 ` [EXTERNAL] " 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=f3514471-9978-4aad-af40-e4970827a61b@web.de \
--to=markus.elfring@web.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=sumang@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
all inboxes | Powered by JetHome®