From: Philip Li <philip.li@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Richard Weinberger <richard@nod.at>,
Eric Biggers <ebiggers@kernel.org>,
Azeem Shaikh <azeemshaikh38@gmail.com>,
Maxim Krasnyansky <maxk@qti.qualcomm.com>,
anton ivanov <anton.ivanov@cambridgegreys.com>,
linux-hardening <linux-hardening@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-um <linux-um@lists.infradead.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
kernel test robot <lkp@intel.com>
Subject: Re: Reported-by/Closes tag for uncommitted issues (was: Re: [PATCH v2] uml: Replace strlcpy with strscpy)
Date: Wed, 7 Jun 2023 17:47:41 +0800 [thread overview]
Message-ID: <ZIBSPW0NYWaY4JFj@rli9-mobl> (raw)
In-Reply-To: <4b1c8af737eb5bccba12883f32ec43f9f292f70f.camel@sipsolutions.net>
On Wed, Jun 07, 2023 at 11:43:11AM +0200, Johannes Berg wrote:
> On Wed, 2023-06-07 at 17:39 +0800, Philip Li wrote:
> >
> > Is that ok we just take this phrase as a quick improvement for first step, which
> > is
> >
> > "If you fix the issue in a separate patch/commit (i.e. not just a new
> > version of the same patch/commit), kindly add following tags:"
> >
> > This could help remind for most cases if not all. Also this allows us
> > not doing "complex" judgement by the bot itself.
>
> Sure, feel free. But yeah, that was the idea, that the decision logic
> wouldn't really need to be in the bot, that feels very difficult.
>
> Maybe someone else on the thread will have a better suggestion :)
Thanks a lot, we will adjust the phrase like this as initial step to resolve
some confusions. And as you said, we welcome more suggestions to improve
the bot.
>
>
> johannes
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
prev parent reply other threads:[~2023-06-07 9:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 18:24 [PATCH v2] uml: Replace strlcpy with strscpy Azeem Shaikh
2023-06-06 20:51 ` Richard Weinberger
2023-06-06 21:08 ` Azeem Shaikh
2023-06-07 4:23 ` Eric Biggers
2023-06-07 8:28 ` Reported-by/Closes tag for uncommitted issues (was: Re: [PATCH v2] uml: Replace strlcpy with strscpy) Johannes Berg
2023-06-07 8:34 ` Richard Weinberger
2023-06-07 9:10 ` Philip Li
2023-06-07 9:17 ` Johannes Berg
2023-06-07 9:39 ` Philip Li
2023-06-07 9:43 ` Johannes Berg
2023-06-07 9:47 ` Philip Li [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=ZIBSPW0NYWaY4JFj@rli9-mobl \
--to=philip.li@intel.com \
--cc=Jason@zx2c4.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=azeemshaikh38@gmail.com \
--cc=ebiggers@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=lkp@intel.com \
--cc=maxk@qti.qualcomm.com \
--cc=richard@nod.at \
/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;
as well as URLs for NNTP newsgroup(s).