public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	John Ogness <john.ogness@linutronix.de>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] more printk for 6.15
Date: Thu, 3 Apr 2025 11:34:54 +0200	[thread overview]
Message-ID: <Z-5VvJsjrRN_lFSt@pathway.suse.cz> (raw)
In-Reply-To: <CAHk-=wgWT4AOFgMxSBVqYD9dVPXTr775UAwyX9cUOz=0ahf3_Q@mail.gmail.com>

On Wed 2025-04-02 12:10:08, Linus Torvalds wrote:
> On Wed, 2 Apr 2025 at 12:07, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > The whole "link to original submission" is garbage.
> 
> Just to clarify: people should link to the *problem* report. Or to the
> *debugging* thread.
> 
> But linking to the final result is pointless. That's what in the tree,
> and any subsequent discussion about it is stale and late.

I agree that links to the threads where the discussion
happened might be more useful.

I personally use the link (added by b4 am -l) when doing
a code archeology. It often points to a whole patchset with
a cover leter. And it sometimes help to understand
the missing context.

Google is a good alternative. But the link is faster
and reliable.

Of course, the best situation is when the commit message
is good enough and the link is not needed. Which reminds
me that anything which triggered a useful discussion should
be explained in the commit message. I need to care more
about this.

Best Regards,
Petr

PS: The #pragma was discussed in v1 thread, see
    https://lore.kernel.org/r/87iko2ear3.fsf@prevas.dk
    

  parent reply	other threads:[~2025-04-03  9:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02 12:58 [GIT PULL] more printk for 6.15 Petr Mladek
2025-04-02 17:12 ` Linus Torvalds
2025-04-02 18:39   ` Andy Shevchenko
2025-04-02 19:06     ` Linus Torvalds
2025-04-02 19:25       ` Andy Shevchenko
2025-04-02 20:34         ` Nathan Chancellor
2025-04-03 12:07           ` Andy Shevchenko
2025-04-04  8:19             ` Petr Mladek
2025-04-04 21:02               ` Nathan Chancellor
2025-04-03 16:14         ` Kees Cook
2025-04-02 19:07     ` Linus Torvalds
2025-04-02 19:10       ` Linus Torvalds
2025-04-02 19:44         ` Steven Rostedt
2025-04-02 19:52           ` Linus Torvalds
2025-04-02 20:25           ` Andy Shevchenko
2025-04-02 20:00         ` Sean Christopherson
2025-04-02 20:11           ` Steven Rostedt
2025-04-03  9:34         ` Petr Mladek [this message]
2025-04-02 17:48 ` 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=Z-5VvJsjrRN_lFSt@pathway.suse.cz \
    --to=pmladek@suse.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=torvalds@linux-foundation.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