From: Dan Carpenter <dan.carpenter@oracle.com>
To: Oleg Drokin <green@whamcloud.com>
Cc: "Reshetova, Elena" <elena.reshetova@intel.com>,
"smatch@vger.kernel.org" <smatch@vger.kernel.org>,
"Kleen, Andi" <andi.kleen@intel.com>
Subject: Re: Smatch mailing list archives
Date: Tue, 11 May 2021 16:40:47 +0300 [thread overview]
Message-ID: <20210511134047.GV1922@kadam> (raw)
In-Reply-To: <F070A889-8B98-4723-9F05-1BC44C4051D6@whamcloud.com>
Generally I just report the bugs and forget about them. If I send a
patch, then I'll review all the warnings from the file and so maybe I'll
see a case where the bug report was overlooked.
I've only seen one case where we merged a fix and then accidentally
merged the buggy code back again the next week. All the kernel bots had
marked it as old so the bug wasn't caught until later.
Actually that's not true. Back in the day there used to be giant SCSI
drivers that did their work out of the tree. Then twice a year they
would do a massive code dump and over write all the fixes that upstream
had merged. :P But that never happens now.
regards,
dan carpenter
next prev parent reply other threads:[~2021-05-11 13:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CY4PR1101MB2326F684A9371A12746211FFE7579@CY4PR1101MB2326.namprd11.prod.outlook.com>
2021-05-07 14:22 ` Smatch mailing list archives Reshetova, Elena
2021-05-08 5:16 ` Dan Carpenter
2021-05-10 6:17 ` Reshetova, Elena
2021-05-10 6:59 ` Oleg Drokin
2021-05-10 9:31 ` Reshetova, Elena
2021-05-10 14:13 ` Oleg Drokin
2021-05-11 13:40 ` Dan Carpenter [this message]
2021-05-11 14:10 ` Reshetova, Elena
2021-05-10 7:20 ` Dan Carpenter
2021-05-10 9:43 ` Reshetova, Elena
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=20210511134047.GV1922@kadam \
--to=dan.carpenter@oracle.com \
--cc=andi.kleen@intel.com \
--cc=elena.reshetova@intel.com \
--cc=green@whamcloud.com \
--cc=smatch@vger.kernel.org \
/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