From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Lee Jones <lee@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Crutcher Dunnavant <crutcher+kernel@datastacks.com>,
Juergen Quade <quade@hsnr.de>,
David Laight <David.Laight@aculab.com>
Subject: Re: [PATCH v3 1/1] lib/vsprintf: Implement spprintf() to catch truncated strings
Date: Thu, 1 Feb 2024 15:25:42 +0200 [thread overview]
Message-ID: <Zbub1upDDLN9JWne@smile.fi.intel.com> (raw)
In-Reply-To: <20240201123004.GA938078@google.com>
On Thu, Feb 01, 2024 at 12:30:04PM +0000, Lee Jones wrote:
> On Thu, 01 Feb 2024, Andy Shevchenko wrote:
> > On Tue, Jan 30, 2024 at 04:09:53PM +0000, Lee Jones wrote:
...
> > > [0] https://lwn.net/Articles/69419/
> > > [1] https://github.com/KSPP/linux/issues/105
> >
> > Link: ... [0]
> > Link: ... [1]
>
> OOI, what does that do?
>
> Does tooling pick-up on them?
Yes, b4 shows them when you do `b4 am` and then you can click from the
terminal.
> These links are for humans.
No objections on this.
> Is there documentation I can go look at?
https://docs.kernel.org/process/submitting-patches.html
"If related discussions or any other background information behind the change
can be found on the web, add 'Link:' tags pointing to it."
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-02-01 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 16:09 [PATCH v3 1/1] lib/vsprintf: Implement spprintf() to catch truncated strings Lee Jones
2024-02-01 11:49 ` Andy Shevchenko
2024-02-01 12:30 ` Lee Jones
2024-02-01 13:25 ` Andy Shevchenko [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=Zbub1upDDLN9JWne@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=David.Laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=crutcher+kernel@datastacks.com \
--cc=lee@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=quade@hsnr.de \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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 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.