public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Alex Hung <alex.hung@amd.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Harry Wentland <harry.wentland@amd.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Sasha Levin <sashal@kernel.org>
Subject: linux-next: manual merge of the jc_docs tree with the mm-nomm-stable tree
Date: Tue, 31 Mar 2026 13:27:08 +0100	[thread overview]
Message-ID: <acu9nEoNNDLSiu6i@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1618 bytes --]

Hi all,

Today's linux-next merge of the jc_docs tree got a conflict in:

  scripts/checkpatch.pl

between commit:

  d1db4118489ff ("checkpatch: add support for Assisted-by tag")

from the mm-nomm-stable tree and commit:

  8545d9bc4bd08 ("scripts/checkpatch: add Assisted-by: tag validation")

from the jc_docs tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

(The mm version does seem to misidentify as a signoff)

diff --cc scripts/checkpatch.pl
index 60fd2ee2d0e58,b8d961d77ff4e..0000000000000
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@@ -3106,11 -3106,11 +3106,11 @@@ sub process 
  				}
  			}
  
 -# Assisted-by: uses format AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2] instead of email
 +			# Assisted-by uses AGENT_NAME:MODEL_VERSION format, not email
- 			if ($sign_off =~ /^Assisted-by:/i) {
- 				if ($email !~ /^\S+:\S+/) {
- 					WARN("BAD_SIGN_OFF",
- 					     "Assisted-by expects 'AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]' format\n" . $herecurr);
+ 			if ($sign_off =~ /^assisted-by:$/i) {
+ 				if ($email !~ /^[^:]+:\S+(\s+\S+)*$/) {
+ 					WARN("BAD_ASSISTED_BY",
+ 					     "Assisted-by: should use format: 'Assisted-by: AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]'\n" . $herecurr);
  				}
  				next;
  			}

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2026-03-31 12:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 12:27 Mark Brown [this message]
2026-03-31 13:15 ` linux-next: manual merge of the jc_docs tree with the mm-nomm-stable tree Jonathan Corbet
  -- strict thread matches above, loose matches on Subject: below --
2026-01-26 16:41 Mark

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=acu9nEoNNDLSiu6i@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alex.hung@amd.com \
    --cc=corbet@lwn.net \
    --cc=harry.wentland@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sashal@kernel.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