From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Conor.Dooley@microchip.com, wangjianli@cdjrlc.com,
damien.lemoal@opensource.wdc.com
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/ata: fix repeated words in comments
Date: Thu, 08 Sep 2022 10:03:56 -0400 [thread overview]
Message-ID: <154c64feea4b2942698c6b96370f78a509048605.camel@HansenPartnership.com> (raw)
In-Reply-To: <a9052683-13a2-1e90-db90-ca9410fafd89@microchip.com>
On Thu, 2022-09-08 at 13:09 +0000, Conor.Dooley@microchip.com wrote:
[...]
> If there's a tool running against this stuff but maintainers are not
> applying the patches as the "fixes" are not fixes it's only going to
> keep generating the same patches over and over is it not?
That's up to the maintainers, but it's fairly easy to ignore patches
from given sources however often they are repeated. There's a lot of
wrong patches that keep getting repeated ...
My own take is that the value would be marginal if all the patches were
correct, but they could be applied with minimal effort using patch
automation. Once you have to verify correctness of each patch, I don't
think the tracking and verification effort is worth the marginal
improvement, but that's a maintainer call.
Regards,
James
next prev parent reply other threads:[~2022-09-08 14:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 12:49 [PATCH] drivers/ata: fix repeated words in comments wangjianli
2022-09-08 12:56 ` Conor.Dooley
2022-09-08 13:02 ` James Bottomley
2022-09-08 13:09 ` Conor.Dooley
2022-09-08 14:03 ` James Bottomley [this message]
2022-09-10 8:24 ` Damien Le Moal
-- strict thread matches above, loose matches on Subject: below --
2022-09-08 12:48 wangjianli
2022-08-25 12:36 Jilin Yuan
2022-08-25 22:27 ` Damien Le Moal
2022-07-10 5:22 Jilin Yuan
2022-07-10 14:21 ` James Bottomley
2022-07-10 23:11 ` Damien Le Moal
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=154c64feea4b2942698c6b96370f78a509048605.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=Conor.Dooley@microchip.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangjianli@cdjrlc.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