From: Dan Williams <dan.j.williams@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Dan Williams <dan.j.williams@intel.com>
Cc: Sedat Dilek <sedat.dilek@gmail.com>,
Johan Hovold <johan@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-cxl@vger.kernel.org>, <mcgrof@kernel.org>
Subject: Re: Revert "module: error out early on concurrent load of the same module file"
Date: Tue, 30 May 2023 16:04:11 -0700 [thread overview]
Message-ID: <647680eb675cb_1c5f629485@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <CAHk-=whHjT-KWPjQK8iSaHJa7WX_LuKgZt_iX+jDxRxDD2Zjdg@mail.gmail.com>
Linus Torvalds wrote:
> On Tue, May 30, 2023 at 6:19 PM Dan Williams <dan.j.williams@intel.com> wrote:
> >
> > I know that the "Link:" for "mailing-list thread where patch originated"
> > is mostly useless information [1], but when it comes to quickly reporting
> > test results on the output of "git bisect", it comes in handy.
>
> It was literally there in this case. We had multiple links, and you
> may just have been overwhelmed by the pure cornucopia of links.
>
> In this case is was the third one:
>
> Link: https://lore.kernel.org/lkml/ZG%2Fa+nrt4%2FAAUi5z@bombadil.infradead.org/
> [3]
>
> which linked to that thread.
>
> It's the links to pure patch submissions that are useless (ie the
> "this is where I sent the patch"). Those lore can find for you
> automatically.
>
> Links to actual threads with background and test commentary are
> useful, and I add those myself. There were several of them.
Yes, my bad, I was lost in the cornucopia of that thread.
next prev parent reply other threads:[~2023-05-30 23:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 16:18 Sedat Dilek
2023-05-29 17:33 ` Linus Torvalds
2023-05-30 3:37 ` Sedat Dilek
2023-05-30 21:43 ` Dan Williams
2023-05-30 21:56 ` Linus Torvalds
2023-05-30 22:19 ` Dan Williams
2023-05-30 22:42 ` Linus Torvalds
2023-05-30 23:04 ` Dan Williams [this message]
2023-05-30 21:58 ` Revert "module: error out early on concurrent load of the same module file"' Luis Chamberlain
2023-05-30 22:21 ` Dan Williams
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=647680eb675cb_1c5f629485@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=johan@kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=sedat.dilek@gmail.com \
--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
all inboxes | Powered by JetHome®