mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Josef Bacik <josef@toxicpanda.com>,
	linux-kernel@vger.kernel.org,
	 Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable <stable@kernel.org>
Subject: [PATCH 0/9] w1: a bunch of llm-found fixes
Date: Tue, 27 Oct 2026 17:04:33 +0100	[thread overview]
Message-ID: <20261027-llm-char-misc-w1-v1-0-d2e6bfafb6a4@linuxfoundation.org> (raw)

Here's a series of some small llm-found fixes that have been sent to me
recently.  Most of them are just minor bugfixes and locking cleanups,
but they are good to have from what I can tell.

Submitting them here to get a solid Sashiko run.  If they seem sane, and
you want me to take these directly through my char-misc tree I can do
that now, or I can gladly wait for you to resend them if you wish to do
that instead.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
Josef Bacik (9):
      w1: use the bus mutex for the "rw" file
      w1: remove the master's files before taking its locks
      w1: ds2482: set the strong pull-up with its byte
      w1: ds28e04: use the bus mutex to talk on the bus
      w1: ds2805: use the bus mutex to talk on the bus
      w1: netlink: drop the slave after the bus is unlocked
      w1: don't hold list_mutex while a slave is torn down
      w1: w1_therm: lock the list of slaves for the bulk read
      w1: w1_therm: leave the slaves of other families alone

 drivers/w1/masters/ds2482.c    | 36 +++++++++++++++++++--------------
 drivers/w1/slaves/w1_ds2805.c  |  8 ++++----
 drivers/w1/slaves/w1_ds28e04.c | 18 ++++++++---------
 drivers/w1/slaves/w1_therm.c   | 45 +++++++++++++++++++++++++++++-------------
 drivers/w1/w1.c                | 21 +++++++++++++-------
 drivers/w1/w1_int.c            |  8 +++++++-
 drivers/w1/w1_netlink.c        |  8 +++++---
 7 files changed, 91 insertions(+), 53 deletions(-)
---
base-commit: d135ab453a7400a34930bdda1ef4bdc8acfac80e
change-id: 20261027-llm-char-misc-w1-cc0ff4fda7d2

Best regards,
--  
Greg Kroah-Hartman <gregkh@linuxfoundation.org>


             reply	other threads:[~2026-10-27 16:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 16:04 Greg Kroah-Hartman [this message]
2026-10-27 16:04 ` [PATCH 1/9] w1: use the bus mutex for the "rw" file Greg Kroah-Hartman
2026-10-27 16:04 ` [PATCH 2/9] w1: remove the master's files before taking its locks Greg Kroah-Hartman
2026-10-27 16:04 ` [PATCH 3/9] w1: ds2482: set the strong pull-up with its byte Greg Kroah-Hartman
2026-10-27 16:04 ` [PATCH 4/9] w1: ds28e04: use the bus mutex to talk on the bus Greg Kroah-Hartman
2026-10-27 16:04 ` [PATCH 5/9] w1: ds2805: " Greg Kroah-Hartman
2026-10-27 16:04 ` [PATCH 6/9] w1: netlink: drop the slave after the bus is unlocked Greg Kroah-Hartman
2026-10-27 16:04 ` [PATCH 7/9] w1: don't hold list_mutex while a slave is torn down Greg Kroah-Hartman
2026-10-27 16:04 ` [PATCH 8/9] w1: w1_therm: lock the list of slaves for the bulk read Greg Kroah-Hartman
2026-10-27 16:04 ` [PATCH 9/9] w1: w1_therm: leave the slaves of other families alone Greg Kroah-Hartman

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=20261027-llm-char-misc-w1-v1-0-d2e6bfafb6a4@linuxfoundation.org \
    --to=gregkh@linuxfoundation.org \
    --cc=josef@toxicpanda.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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

all inboxes | Powered by JetHome®