All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: patchwork-bot+netdevbpf@kernel.org
Cc: David Yang <mmyangfl@gmail.com>,
	netdev@vger.kernel.org, andrew@lunn.ch, olteanv@gmail.com,
	davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v12 0/5] net: dsa: motorcomm: Add LED support
Date: Thu, 3 Sep 2026 10:57:16 -0700	[thread overview]
Message-ID: <20260903105716.5c163da2@kernel.org> (raw)
In-Reply-To: <178840621563.3072235.4183497708325455365.git-patchwork-notify@kernel.org>

On Thu, 03 Sep 2026 03:30:15 +0000 patchwork-bot+netdevbpf@kernel.org
wrote:
>   - [net-next,v12,4/5] net: dsa: motorcomm: Add LED support
>     (no matching commit)

Sigh, I thought you said all the issues on v11 were false positives.
I merged v11, please send an incremental fix.

      reply	other threads:[~2026-09-03 17:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03  3:16 [PATCH net-next v12 0/5] net: dsa: motorcomm: Add LED support David Yang
2026-09-03  3:16 ` [PATCH net-next v12 1/5] net: dsa: yt921x: Check lock status with lockdep_assert_held_once() David Yang
2026-09-03  3:16 ` [PATCH net-next v12 2/5] net: dsa: motorcomm: Move to subdirectory David Yang
2026-09-03  3:16 ` [PATCH net-next v12 3/5] net: dsa: motorcomm: Split SMI module David Yang
2026-09-03  3:16 ` [PATCH net-next v12 4/5] net: dsa: motorcomm: Add LED support David Yang
2026-09-04  3:17   ` sashiko-bot
2026-09-03  3:16 ` [PATCH net-next v12 5/5] dt-bindings: net: dsa: yt921x: Add LEDs definition example David Yang
2026-09-03  3:30 ` [PATCH net-next v12 0/5] net: dsa: motorcomm: Add LED support patchwork-bot+netdevbpf
2026-09-03 17:57   ` Jakub Kicinski [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=20260903105716.5c163da2@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmyangfl@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=patchwork-bot+netdevbpf@kernel.org \
    --cc=robh@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 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.