From: Lee Jones <lee@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Fei Shao <fshao@chromium.org>, Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH] leds: pwm: Fix an error code
Date: Wed, 12 Jul 2023 14:07:50 +0100 [thread overview]
Message-ID: <20230712130750.GE10768@google.com> (raw)
In-Reply-To: <CAHp75Vd4cuNEQUotVZb8Xu+JMC9KKUk_Gg5N_YsA2KoEANwBKw@mail.gmail.com>
On Wed, 12 Jul 2023, Andy Shevchenko wrote:
> On Wed, Jul 12, 2023 at 3:00 PM Lee Jones <lee@kernel.org> wrote:
> > On Tue, 11 Jul 2023, Andy Shevchenko wrote:
> >
> > > On Tue, Jul 11, 2023 at 11:31 AM Fei Shao <fshao@chromium.org> wrote:
> > > >
> > > > Use the negated -EINVAL as the error code.
> > >
> > > Thank you, it seems Dan had been the first one.
> > >
> > > Message ID <a33b981a-b2c4-4dc2-b00a-626a090d2f11@moroto.mountain>
> >
> > I don't know much about how other people operate, but I have no way to
> > trivially navigate to this. Would you be kind enough to use URLs
> > please?
>
> Use this pattern:
> https://lore.kernel.org/r/$MSG_ID
> where $MSG_ID is a33b981a-b2c4-4dc2-b00a-626a090d2f11@moroto.mountain
> in this case.
>
> Hence, the URL:
> https://lore.kernel.org/r/a33b981a-b2c4-4dc2-b00a-626a090d2f11@moroto.mountain
>
> Easier way is simply run `b4 mbox $MSG_ID` and open the loaded mbox
> with your preferred MUA.
Right, I'm aware that I can manually manipulate the lore URL in this way.
However I, like many, do not have a way to do this easily from my mailer.
This is why directly navigatable / clickable URLs were invented. :)
Please could you use full / clickable URLs to messages?
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2023-07-12 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 8:30 [PATCH] leds: pwm: Fix an error code Fei Shao
2023-07-11 9:09 ` Andy Shevchenko
2023-07-11 9:20 ` Fei Shao
2023-07-12 12:00 ` Lee Jones
2023-07-12 12:49 ` Andy Shevchenko
2023-07-12 13:07 ` Lee Jones [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=20230712130750.GE10768@google.com \
--to=lee@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=fshao@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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