From: bugzilla-daemon@kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 216095] sysfs: cannot create duplicate filename '/devices/platform/of-display'
Date: Wed, 12 Apr 2023 00:33:46 +0000 [thread overview]
Message-ID: <bug-216095-206035-70NTbFHodA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216095-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216095
Michael Ellerman (michael@ellerman.id.au) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
CC| |michael@ellerman.id.au
Resolution|OBSOLETE |CODE_FIX
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2023-04-12 0:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 22:23 [Bug 216095] New: sysfs: cannot create duplicate filename '/devices/platform/of-display' bugzilla-daemon
2022-06-08 22:24 ` [Bug 216095] " bugzilla-daemon
2022-06-14 14:01 ` [Bug 216095] New: " Michael Ellerman
2022-06-15 11:28 ` Erhard F.
2022-08-15 23:29 ` [Bug 216095] " bugzilla-daemon
2022-08-15 23:30 ` bugzilla-daemon
2022-08-16 0:11 ` bugzilla-daemon
2022-11-14 23:52 ` bugzilla-daemon
2022-11-14 23:53 ` bugzilla-daemon
2022-12-31 15:22 ` bugzilla-daemon
2022-12-31 15:22 ` bugzilla-daemon
2023-01-02 6:10 ` bugzilla-daemon
2023-01-08 14:58 ` bugzilla-daemon
2023-01-08 15:01 ` bugzilla-daemon
2023-01-09 10:00 ` bugzilla-daemon
2023-01-14 13:11 ` bugzilla-daemon
2023-01-14 13:12 ` bugzilla-daemon
2023-01-17 17:07 ` bugzilla-daemon
2023-02-23 15:11 ` bugzilla-daemon
2023-04-12 0:33 ` bugzilla-daemon [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=bug-216095-206035-70NTbFHodA@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).