From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Marek Vasut <marex@denx.de>, linux-i2c@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Thorsten Leemhuis <regressions@leemhuis.info>
Subject: Re: [PATCH] nvmem: core: Check read_only flag for force_ro in bin_attr_nvmem_write()
Date: Sat, 26 Oct 2024 08:21:02 +0100 [thread overview]
Message-ID: <d8b903ff-4a66-4d9d-8bad-099ff9d83a54@linaro.org> (raw)
In-Reply-To: <d2b8f767-c5c9-409d-a6fa-1c101b90c9fc@denx.de>
Apologies, some how I missed this email.
On 26/10/2024 00:15, Marek Vasut wrote:
> On 9/25/24 12:42 AM, Marek Vasut wrote:
>> On 7/13/24 5:39 PM, Marek Vasut wrote:
>>> The bin_attr_nvmem_write() must check the read_only flag and block
>>> writes on read-only devices, now that a nvmem device can be switched
>>> between read-write and read-only mode at runtime using the force_ro
>>> attribute. Add the missing check.
>>>
>>> Fixes: 9d7eb234ac7a ("nvmem: core: Implement force_ro sysfs attribute")
>>> Signed-off-by: Marek Vasut <marex@denx.de>
Applied with CC stable.
--srini
>>> ---
>>> Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
>>> Cc: linux-kernel@vger.kernel.org
>> It seems this bugfix is not even in next, any news ?
>
> This is still broken, bugfix is available for three months now, but not
> picked up. Any news?
next prev parent reply other threads:[~2024-10-26 7:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 15:39 Marek Vasut
2024-09-24 22:42 ` Marek Vasut
2024-10-25 23:15 ` Marek Vasut
2024-10-26 7:21 ` Srinivas Kandagatla [this message]
2024-10-26 7:36 ` Marek Vasut
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=d8b903ff-4a66-4d9d-8bad-099ff9d83a54@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=regressions@leemhuis.info \
/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®