From: "Theodore Ts'o" <tytso@mit.edu>
To: Borislav Petkov <bp@alien8.de>
Cc: Thorsten Leemhuis <linux@leemhuis.info>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Zhangfei Gao <zhangfei.gao@foxmail.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: Link: tag and links to submission and reports (was: Re: [GIT pull] core/urgent for v5.18-rc6)
Date: Wed, 11 May 2022 11:50:07 -0400 [thread overview]
Message-ID: <YnvbLx9FKgQwZJ/F@mit.edu> (raw)
In-Reply-To: <Ynt1z0eZ19eMqp8I@zn.tnic>
On Wed, May 11, 2022 at 10:37:35AM +0200, Borislav Petkov wrote:
> - The problem is when the discussion happened somewhere and the patch
> got submitted separately. I can't think of a good way to automate
> that so we have to pay attention and fix the link tag by hand and add
> the relevant one. And I try to do that when I'm especially awake when
> applying the patch.
I would argue that it should be the patch submitter's responsibility
to explicitly add a URL to the problem report. In some cases this
might be a pointer to a bug tracking system; in other cases it might
be a URL to lore.kernel.org.
- Ted
next prev parent reply other threads:[~2022-05-11 15:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 12:05 [GIT pull] core/urgent for v5.18-rc6 Thomas Gleixner
2022-05-08 12:05 ` [GIT pull] irq/urgent " Thomas Gleixner
2022-05-08 18:40 ` pr-tracker-bot
2022-05-08 12:05 ` [GIT pull] locking/urgent " Thomas Gleixner
2022-05-08 18:40 ` pr-tracker-bot
2022-05-08 12:05 ` [GIT pull] timers/urgent " Thomas Gleixner
2022-05-08 18:40 ` pr-tracker-bot
2022-05-08 12:07 ` [GIT pull] x86/urgent " Thomas Gleixner
2022-05-08 18:40 ` pr-tracker-bot
2022-05-08 18:00 ` [GIT pull] core/urgent " Linus Torvalds
2022-05-08 18:09 ` Linus Torvalds
2022-05-08 18:36 ` Linus Torvalds
2022-05-09 15:02 ` Jean-Philippe Brucker
2022-05-10 11:27 ` Link: tag and links to submission and reports (was: Re: [GIT pull] core/urgent for v5.18-rc6) Thorsten Leemhuis
2022-05-11 8:37 ` Borislav Petkov
2022-05-11 13:48 ` Michael Ellerman
2022-05-11 15:50 ` Theodore Ts'o [this message]
2022-05-11 15:55 ` Linus Torvalds
2022-05-11 19:35 ` Borislav Petkov
2022-05-12 8:43 ` Thorsten Leemhuis
2022-08-04 9:29 ` Borislav Petkov
2022-05-11 22:37 ` Theodore Ts'o
2022-05-08 18:40 ` [GIT pull] core/urgent for v5.18-rc6 pr-tracker-bot
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=YnvbLx9FKgQwZJ/F@mit.edu \
--to=tytso@mit.edu \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=fenghua.yu@intel.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jean-philippe@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=zhangfei.gao@foxmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome