From: Vlastimil Babka <vbabka@suse.cz>
To: Dan Carpenter <error27@gmail.com>,
oe-kbuild@lists.linux.dev, lkp@intel.com
Cc: Hillf Danton <hdanton@sina.com>,
Masami Ichikawa <masami.ichikawa@miraclelinux.com>,
cip-dev <cip-dev@lists.cip-project.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org, lwn@lwn.net,
smatch@vger.kernel.org
Subject: Re: Who is looking at CVEs to prevent them?
Date: Wed, 8 Mar 2023 08:52:33 +0100 [thread overview]
Message-ID: <651ee4e5-b298-606e-938f-0e49fdf295c3@suse.cz> (raw)
In-Reply-To: <6d1ad8e9-2bec-4cd4-b4dd-595c88855274@kili.mountain>
On 3/7/23 12:53, Dan Carpenter wrote:
> On Tue, Mar 07, 2023 at 12:42:03PM +0100, Vlastimil Babka wrote:
>> Why do you keep adding linux-mm to the Cc list of random threads that are
>> not about MM?
>
> That's kbuild-bot stuff. The kbuild-bot generates those emails and I
> just look them over and hit send.
Sorry, wasn't clear that I was asking Hillf who did the Cc on this
thread and other threads (not only kbuild bot threads).
> I don't why the kbuild bot CCs linux-mm either... Let me ask the devs
> about that. A lot of the -mm warning are correct but just the CC list
> is weird.
Sure, it's fine if a bug is suspected to be mm related that linux-mm is
Cc'd, even if it turns out a wrong guess in the end.
> The kbuild-bot stuff is really nice for me. The kbuild-bot doesn't use
> the cross function DB so everything is local to the function and easy to
> review.
>
> regards,
> dan carpenter
>
>
next prev parent reply other threads:[~2023-03-08 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAODzB9qjdhQkZ+tALHpDLHoK7GAf8Uybfzp8mxXt=Dwnn_0RjA@mail.gmail.com>
[not found] ` <59f7f076-a9d5-4bfb-a6da-bbe0a7567688@kili.mountain>
2023-03-07 11:00 ` Hillf Danton
2023-03-07 11:32 ` Dan Carpenter
2023-03-07 11:42 ` Vlastimil Babka
2023-03-07 11:53 ` Dan Carpenter
2023-03-08 7:52 ` Vlastimil Babka [this message]
2023-03-07 12:47 ` Hillf Danton
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=651ee4e5-b298-606e-938f-0e49fdf295c3@suse.cz \
--to=vbabka@suse.cz \
--cc=cip-dev@lists.cip-project.org \
--cc=error27@gmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=lwn@lwn.net \
--cc=masami.ichikawa@miraclelinux.com \
--cc=oe-kbuild@lists.linux.dev \
--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