MPTCP Linux Development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v4 3/3] checkpatch: skip warnings for symbol links
Date: Mon, 13 May 2024 12:44:27 +0200	[thread overview]
Message-ID: <602f2d3e-22b0-47e3-ba7c-0015468a3d72@kernel.org> (raw)
In-Reply-To: <1628d78e12809ff0f4dd0526f6addbbf00dae66b.1715503185.git.tanggeliang@kylinos.cn>

Hi Geliang,

On 12/05/2024 10:41, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
> 
> If there is a symbol link in the given patch, checkpatch.pl reports two
> inaccurate warnings:

Good idea to fix that!

Do you mind sending it as a separated patch to CheckPatch maintainers
directly?

It might be good to split it in 2, with 2 different Fixes tag, to help
with the backports.

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  reply	other threads:[~2024-05-13 10:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-12  8:41 [PATCH mptcp-next v4 0/3] patches for new MPTCP subflow subtest Geliang Tang
2024-05-12  8:41 ` [PATCH mptcp-next v4 1/3] selftests/bpf: Add mptcp pm_nl_ctl link Geliang Tang
2024-05-12  8:41 ` [PATCH mptcp-next v4 2/3] Squash to "selftests/bpf: Add mptcp subflow subtest" Geliang Tang
2024-05-13 10:38   ` Matthieu Baerts
2024-05-12  8:41 ` [PATCH mptcp-next v4 3/3] checkpatch: skip warnings for symbol links Geliang Tang
2024-05-13 10:44   ` Matthieu Baerts [this message]
2024-05-15 16:43   ` Matthieu Baerts
2024-05-12  9:34 ` [PATCH mptcp-next v4 0/3] patches for new MPTCP subflow subtest MPTCP CI

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=602f2d3e-22b0-47e3-ba7c-0015468a3d72@kernel.org \
    --to=matttbe@kernel.org \
    --cc=geliang@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=tanggeliang@kylinos.cn \
    /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