From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: "Krzysztof Wilczyński" <kw@linux.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Sasha Levin <sashal@kernel.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: endpoint: Use sysfs_emit() in "show" functions
Date: Tue, 20 Jul 2021 10:08:51 +0900 [thread overview]
Message-ID: <6d10e89b-3518-faff-e320-6d03013567a1@socionext.com> (raw)
In-Reply-To: <20210719151837.GA473693@rocinante>
Hi Krzysztof,
On 2021/07/20 0:18, Krzysztof Wilczy?ski wrote:
> [+cc Sasha for visibility]
>
> Hi!
>
> [...]
>>> Nice catch!
>>
>> I actually executed "cat" against configfs to meet the issue and found
>> your solution in pci-sysfs.
>
> Oh! That's not good... I am curious, which attribute caused this?
Sorry I misunderstood.
I found this "cat" issue on next-20210713 and all configfs attribues had
the same issue.
However, my patch wasn't the solution for the issue. This has been fixed by
7fe1e79b59ba ("configfs: implement the .read_iter and .write_iter methods").
The function replacement was found in the process of finding the issue.
> Also, if this is fixing a bug, then it might warrant letting the folks who look
> after the long-term and stable kernels know. I also wonder if there would be
> something to add for the "Fixes:" tag, if there is a previous commit this
> change fixes.
So my patch doesn't fix any issues.
Thank you,
---
Best Regards
Kunihiko Hayashi
prev parent reply other threads:[~2021-07-20 1:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 2:44 Kunihiko Hayashi
2021-07-19 3:43 ` Krzysztof Wilczyński
2021-07-19 14:54 ` Kunihiko Hayashi
2021-07-19 15:18 ` Krzysztof Wilczyński
2021-07-20 1:08 ` Kunihiko Hayashi [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=6d10e89b-3518-faff-e320-6d03013567a1@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=bhelgaas@google.com \
--cc=kishon@ti.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=sashal@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®