[PATCH 1/2] printk: Block console kthreads when direct printing will be required
Linus Torvalds
torvalds at linux-foundation.org
Wed Jun 15 10:47:14 PDT 2022
On Wed, Jun 15, 2022 at 9:28 AM Petr Mladek <pmladek at suse.com> wrote:
>
> BugLink: https://lore.kernel.org/r/20220610205038.GA3050413@paulmck-ThinkPad-P17-Gen-1
> BugLink: https://lore.kernel.org/r/CAMdYzYpF4FNTBPZsEFeWRuEwSies36QM_As8osPWZSr2q-viEA@mail.gmail.com
Other thread discussion about this exact thing:
https://lore.kernel.org/all/CAHk-=wgzRUT1fBpuz3xcN+YdsX0SxqOzHWRtj0ReHpUBb5TKbA@mail.gmail.com/
please stop making up random tags that make no sense.
Just use "Link:"
Look at that first one (I didn't even bother following the second
one). The "bug" part is not even the most important part.
The reason to follow that link is all the discussion, the test-patch,
and the confirmation from Paul that "yup, that patch solves the
problem for me".
It's extra context to the commit, in case somebody wants to know the
history. The "bug" part is (and always should be) already explained in
the commit message, there's absolutely no point in adding soem extra
noise to the "Link:" tag.
And if the only reason for "BugLink:" to exist is to show "look, this
tag actually contains relevant and interesting information", then the
solution to THAT problem is to not have the links that are useless and
pointless in the first place.
Put another way: if you want to distinguish useless links from useful
ones, just do it by not including the useless ones.
Ok?
Linus
More information about the Linux-rockchip
mailing list