netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Christian Marangi <ansuelsmth@gmail.com>,
	Pavel Machek <pavel@ucw.cz>,
	linux-leds@vger.kernel.org, David Miller <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, netdev <netdev@vger.kernel.org>
Subject: [GIT PULL] Immutable branch between LEDs and netdev due for the v6.5 merge window
Date: Thu, 25 May 2023 12:15:21 +0100	[thread overview]
Message-ID: <20230525111521.GA411262@google.com> (raw)
In-Reply-To: <02004a73-2768-46f6-86ad-c6c631631abf@lunn.ch>

> Christian Marangi and I will be continuing the work of offloading LED
> blinking to Ethernet MAC and PHY LED controllers. The next set of
> patches is again cross subsystem, LEDs and netdev. It also requires
> some patches you have in for-leds-next:
> 
> a286befc24e8 leds: trigger: netdev: Use mutex instead of spinlocks
> 509412749002 leds: trigger: netdev: Convert device attr to macro
> 0fd93ac85826 leds: trigger: netdev: Rename add namespace to netdev trigger enum modes
> eb31ca4531a0 leds: trigger: netdev: Drop NETDEV_LED_MODE_LINKUP from mode
> 3fc498cf54b4 leds: trigger: netdev: Recheck NETDEV_LED_MODE_LINKUP on dev rename
> 
> I'm assuming the new series will get nerged via netdev, with your
> Acked-by. Could you create a stable branch with these patches which
> can be pulled into netdev?

-------------

The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:

  Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git ib-leds-netdev-v6.5

for you to fetch changes up to d1b9e1391ab2dc80e9db87fe8b2de015c651e4c9:

  leds: trigger: netdev: Use mutex instead of spinlocks (2023-05-25 12:07:38 +0100)

----------------------------------------------------------------
Immutable branch between LEDs and netdev due for the v6.5 merge window

----------------------------------------------------------------
Christian Marangi (5):
      leds: trigger: netdev: Recheck NETDEV_LED_MODE_LINKUP on dev rename
      leds: trigger: netdev: Drop NETDEV_LED_MODE_LINKUP from mode
      leds: trigger: netdev: Rename add namespace to netdev trigger enum modes
      leds: trigger: netdev: Convert device attr to macro
      leds: trigger: netdev: Use mutex instead of spinlocks

 drivers/leds/trigger/ledtrig-netdev.c | 151 +++++++++++++---------------------
 1 file changed, 59 insertions(+), 92 deletions(-)

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2023-05-25 11:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-19 15:38 Stable branch for LEDs Andrew Lunn
2023-05-25 11:15 ` Lee Jones [this message]
2023-05-26  3:50   ` [GIT PULL] Immutable branch between LEDs and netdev due for the v6.5 merge window patchwork-bot+netdevbpf

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=20230525111521.GA411262@google.com \
    --to=lee@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pavel@ucw.cz \
    /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;
as well as URLs for NNTP newsgroup(s).