mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: akpm@linux-foundation.org, axboe@kernel.dk,
	michel.dagenais@polymtl.ca, richardj_moore@uk.ibm.com,
	bob@watson.ibm.com, karim@opersys.com, zanussi@us.ibm.com,
	linux-kernel@vger.kernel.org, Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH] MAINTAINERS: add RELAY entry
Date: Mon, 2 Mar 2026 10:51:46 +0200	[thread overview]
Message-ID: <aaVPot-hj709Zxox@ashevche-desk.local> (raw)
In-Reply-To: <CAL+tcoA94QxakxNX0CkV=U-PCoOrrJ-hHmQpij6DmijdtmdTpA@mail.gmail.com>

On Mon, Mar 02, 2026 at 04:40:40PM +0800, Jason Xing wrote:
> Hi Andy,
> 
> On Mon, Mar 2, 2026 at 4:35 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Sun, Mar 01, 2026 at 10:09:02AM +0800, Jason Xing wrote:

...

> > > [1]: commit e82894f84dbb ("[PATCH] relayfs")
> > > [2]: commit b86ff981a825 ("[PATCH] relay: migrate from relayfs to
> > > a generic relay API")
> >
> > It's better to read as a single line here
> >
> > [2]: commit b86ff981a825 ("[PATCH] relay: migrate from relayfs to > a generic relay API")
> >
> > OR you can even have it as a proper Link tag:
> >
> > Link: https://git.kernel.org/torvalds/c/b86ff981a825 [2]
> >
> > Same for the rest.
> 
> Thanks for the review.
> 
> The fact is that originally I used a single line but checkpatch warned
> me because of exceeding 75 chars. The current format is just to split
> it into two lines as script requested.

Checkpatch doesn't parse the tags correctly (or lines that can be recognized as
similar to tags). TL;DR: ignore checkpatch for this certain case.

> > > [3]: commit c1bf6959dd81 ("wifi: ath11k: Register relayfs entries
> > > for CFR dump")
> > > [4]: https://lpc.events/event/19/contributions/2055/
> > > [5]: https://lpc.events/event/19/contributions/2010/
> >
> > Note, when converting to Link tags the above, this blank line should be
> > removed.

-- 
With Best Regards,
Andy Shevchenko



      parent reply	other threads:[~2026-03-02  8:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-01  2:09 Jason Xing
2026-03-01 13:38 ` Jens Axboe
2026-03-02  8:35 ` Andy Shevchenko
2026-03-02  8:40   ` Jason Xing
2026-03-02  8:47     ` Jason Xing
2026-03-02  8:54       ` Andy Shevchenko
2026-03-02  9:10         ` Jason Xing
2026-03-02  8:51     ` Andy Shevchenko [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=aaVPot-hj709Zxox@ashevche-desk.local \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=bob@watson.ibm.com \
    --cc=karim@opersys.com \
    --cc=kerneljasonxing@gmail.com \
    --cc=kernelxing@tencent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michel.dagenais@polymtl.ca \
    --cc=richardj_moore@uk.ibm.com \
    --cc=zanussi@us.ibm.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

all inboxes | Powered by JetHome®