From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Krzysztof Olędzki" <ole@ans.pl>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Guenter Roeck <linux@roeck-us.net>,
Bartosz Golaszewski <brgl@bgdev.pl>,
stable@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-hwmon@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Regression caused by "eeprom: at24: Probe for DDR3 thermal sensor in the SPD case" - "sysfs: cannot create duplicate filename"
Date: Mon, 24 Jun 2024 07:43:59 +0200 [thread overview]
Message-ID: <2024062438-patriarch-spendable-96b9@gregkh> (raw)
In-Reply-To: <a57e9a39-13ce-4e4d-a7a1-c591f6b4ac65@ans.pl>
On Sun, Jun 23, 2024 at 11:47:39AM -0700, Krzysztof Olędzki wrote:
> Hi,
>
> After upgrading kernel to Linux 6.6.34 on one of my systems, I noticed "sysfs: cannot create duplicate filename" and i2c registration errors in dmesg, please see below.
>
> This seems to be related to https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.6.y&id=4d5ace787273cb159bfdcf1c523df957938b3e42 - reverting the change fixes the problem.
So is this also an issue in 6.9?
thanks,
greg k-h
next prev parent reply other threads:[~2024-06-24 5:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 18:47 Regression caused by "eeprom: at24: Probe for DDR3 thermal sensor in the SPD case" - "sysfs: cannot create duplicate filename" Krzysztof Olędzki
2024-06-24 5:33 ` Guenter Roeck
2024-06-24 8:38 ` Krzysztof Olędzki
2024-06-24 14:54 ` Guenter Roeck
2024-06-24 16:23 ` Guenter Roeck
2024-06-24 20:58 ` Heiner Kallweit
2024-06-25 3:45 ` Guenter Roeck
2024-06-27 11:29 ` Krzysztof Olędzki
2024-06-27 12:12 ` Krzysztof Olędzki
2024-06-27 11:24 ` Krzysztof Olędzki
2024-06-29 21:56 ` Heiner Kallweit
2024-06-24 5:43 ` Greg Kroah-Hartman [this message]
2024-06-24 13:35 ` Guenter Roeck
2024-07-02 20:25 ` Heiner Kallweit
2024-07-07 1:42 ` Krzysztof Olędzki
2024-07-23 14:12 ` Krzysztof Olędzki
2024-08-03 17:19 ` Heiner Kallweit
2024-08-13 16:28 ` Krzysztof Olędzki
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=2024062438-patriarch-spendable-96b9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=brgl@bgdev.pl \
--cc=hkallweit1@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=ole@ans.pl \
--cc=stable@vger.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