From: "Toke Høiland-Jørgensen" <toke@kernel.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: Felix Fietkau <nbd@nbd.name>, Rosen Penev <rosenp@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] net: ath9k: use devm for request_irq
Date: Thu, 08 Aug 2024 15:54:44 +0200 [thread overview]
Message-ID: <87ed6zp1az.fsf@toke.dk> (raw)
In-Reply-To: <87o7632qff.fsf@kernel.org>
Kalle Valo <kvalo@kernel.org> writes:
> Toke Høiland-Jørgensen <toke@kernel.org> writes:
>
>>> But honestly more and more I'm starting to think that we should just
>>> reject all these "drive-by cleanups". We have better things to do than
>>> fixing unnecessary their bugs. Thoughts?
>>
>> Hmm, yeah, maybe. I do kinda like the fact that people send patches to
>> improve small things, though. We all started out as new to the kernel,
>> and I appreciate the fact that people try to improve our "commons" in
>> this way even if it's small things.
>
> Yeah, you have a point. It's just that the extra work from cleanups
> feels so unnecessary compared to the practical benefits. And most of the
> time we don't hear from these people ever again, that's why I call them
> "drive-by cleanup".
Sure, I share the frustration, and not everyone turns into regular
contributors. But I like to think that even those who don't get
something else out of it at least. And on our side I guess there's a
balance to be struck between being welcoming and not expending too much
effort on it :)
>> I do try to be critical of things that can break stuff before ack'ing
>> these fixes, but I'll admit that it seems like I don't have that great
>> of a track record for judging "correct" in this context (cf this one,
>> and that debugfs regression). So I guess you're right that I should at
>> least raise the bar somewhat; will try to recalibrate and say no more :)
>
> You are doing a great job :) Nobody can catch all bugs in review, I
> would say there is a small percentage (5%?) of all cleanup patches that
> cause issues. Though it would be cool to see some real statistics.
Thanks! Yeah, would love to see some statistics, but I suppose it's not
trivial to identity "cleanup patches" in the first place in a way that
can be automated. Maybe something to poke at sometime one has time to
spare (ha!) or needs a break from the regular drudgery :)
-Toke
prev parent reply other threads:[~2024-08-08 13:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 21:02 [PATCH] net: ath9k: use devm for request_irq Rosen Penev
2024-08-01 8:10 ` Kalle Valo
2024-08-05 12:25 ` Toke Høiland-Jørgensen
2024-08-07 8:08 ` Kalle Valo
2024-08-07 17:47 ` Felix Fietkau
2024-08-07 18:52 ` Rosen Penev
2024-08-07 20:05 ` Felix Fietkau
2024-08-07 20:07 ` Rosen Penev
2024-08-07 20:20 ` Felix Fietkau
2024-08-08 9:25 ` Toke Høiland-Jørgensen
2024-08-08 10:17 ` Kalle Valo
2024-08-08 10:37 ` Toke Høiland-Jørgensen
2024-08-08 11:40 ` Kalle Valo
2024-08-08 13:54 ` Toke Høiland-Jørgensen [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=87ed6zp1az.fsf@toke.dk \
--to=toke@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=rosenp@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.