All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Cunhao Lu <1579567540@qq.com>
Cc: kuba@kernel.org, netdev@vger.kernel.org, davem@davemloft.net,
	edumazet@kernel.org, pabeni@redhat.com, horms@kernel.org,
	mkl@pengutronix.de, mailhol@kernel.org, socketcan@hartkopp.net,
	robin@protonic.nl, o.rempel@pengutronix.de,
	kernel@pengutronix.de, max@enpas.org, linux-can@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] MAINTAINERS: exclude CAN documentation from general networking
Date: Tue, 17 Nov 2026 14:10:04 +0000	[thread overview]
Message-ID: <179492460428.610117.3153920075892405328.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261113-exclude-can-docs-from-netdev-v2-1-8ae9dc553024@qq.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Fri, 13 Nov 2026 10:33:06 +0800 you wrote:
> From: Cunhao Lu <1579567540@qq.com>
> 
> The SocketCAN, ISO-TP and J1939 documents and the CAN driver documentation
> directory match the broad Documentation/networking/ pattern in
> NETWORKING [GENERAL]. This makes get_maintainer.pl select netdev and the
> general networking maintainers for these CAN-specific documentation
> changes.
> 
> [...]

Here is the summary with links:
  - [net,v2] MAINTAINERS: exclude CAN documentation from general networking
    https://git.kernel.org/netdev/net/c/8868b79a430e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-11-17 14:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13  2:33 [PATCH net v2] MAINTAINERS: exclude CAN documentation from general networking Cunhao Lu
2026-11-13  2:33 ` Cunhao Lu via B4 Relay
2026-11-17 14:10 ` patchwork-bot+netdevbpf [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=179492460428.610117.3153920075892405328.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=1579567540@qq.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mailhol@kernel.org \
    --cc=max@enpas.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=pabeni@redhat.com \
    --cc=robin@protonic.nl \
    --cc=socketcan@hartkopp.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.