mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Christian Brauner <brauner@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Lorenzo Stoakes <ljs@kernel.org>, Willy Tarreau <w@1wt.eu>
Subject: Re: linux-next: manual merge of the jc_docs tree with the char-misc.current tree
Date: Thu, 6 Aug 2026 08:19:03 +0200	[thread overview]
Message-ID: <2026080653-tamale-unsworn-43fe@gregkh> (raw)
In-Reply-To: <anMt5iPbjY3hxA6Q@sirena.org.uk>

On Wed, Aug 05, 2026 at 01:34:46PM +0100, Mark Brown wrote:
> Hi all,
> 
> Today's linux-next merge of the jc_docs tree got a conflict in:
> 
>   Documentation/process/coding-assistants.rst
> 
> between commit:
> 
>   3d7c44f73765d ("docs: coding-assistant: explain important steps when looking for bugs")
> 
> from the char-misc.current tree and commits:
> 
>   d699a5da10394 ("docs: link AI coding assistants and tool-generated content pages")
>   816d9992d9ed4 ("coding-assistants: simplify attribution")
> 
> 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.
> 
> diff --cc Documentation/process/coding-assistants.rst
> index e71df7d28467e,e62c9577d91a2..0000000000000
> --- a/Documentation/process/coding-assistants.rst
> +++ b/Documentation/process/coding-assistants.rst
> @@@ -56,41 -56,4 +56,41 @@@ Basic development tools (git, gcc, make
>   
>   Example::
>   
> -   Assisted-by: Claude:claude-3-opus coccinelle sparse
> +   Assisted-by: LLM coccinelle sparse

Looks good to me, thanks!

greg k-h

  reply	other threads:[~2026-08-06  6:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 12:34 Mark Brown
2026-08-06  6:19 ` Greg Kroah-Hartman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-06-20  1:11 Stephen Rothwell
2019-06-20  5:57 ` Greg KH
2019-07-08 23:50 ` Stephen Rothwell

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=2026080653-tamale-unsworn-43fe@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=brauner@kernel.org \
    --cc=broonie@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ljs@kernel.org \
    --cc=w@1wt.eu \
    /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®