From: Rohit Sarkar <rohitsarkar5398@gmail.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: "Sa, Nuno" <Nuno.Sa@analog.com>,
"Ardelean, Alexandru" <alexandru.Ardelean@analog.com>,
"jic23@kernel.org" <jic23@kernel.org>,
"stefan.popa@analog.com" <stefan.popa@analog.com>,
"zhongjiang@huawei.com" <zhongjiang@huawei.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"Bogdan, Dragos" <Dragos.Bogdan@analog.com>,
"pmeerw@pmeerw.net" <pmeerw@pmeerw.net>,
"knaack.h@gmx.de" <knaack.h@gmx.de>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] use DEFINE_DEBUGFS_ATTRIBUTE instead of DEFINE_SIMPLE_ATTRIBUTE
Date: Tue, 31 Mar 2020 17:19:51 +0530 [thread overview]
Message-ID: <5e832e62.1c69fb81.2a0e9.b85d@mx.google.com> (raw)
In-Reply-To: <5e832756.1c69fb81.19c58.78e8@mx.google.com>
Hey Nuno,
> > > >
> > > I don't have the exact parts that this patch is touching but I have other parts where this patch
> > > applies and should be same. So, the idea to test this is to read the files in debugfs? Maybe also
> > > some unbind + binding?
> > >
> > > I will try to test this still today...
> >
> > The stress test is to open the debugfs file, then unbind the device and then
> > read from the still open debugfs file.
> Yes, also just to be sure, we need to test DEFINE_DEBUGFS_ATTRIBUTE
> along with debugfs_create_file_unsafe. I will send out another patch
> that changes debugfs_create_file to debugfs_create_file_unsafe and then
> that can be tested.
Have sent out a v2 that is ready to be tested
> > - Lars
>
> Thanks,
> Rohit
Thanks,
Rohit
next prev parent reply other threads:[~2020-03-31 11:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 6:34 [PATCH 0/2] use DEFINE_DEBUGFS_ATTRIBUTE instead of DEFINE_SIMPLE_ATTRIBUTE Rohit Sarkar
2020-03-28 6:34 ` [PATCH 1/2] iio: imu: adis16400: " Rohit Sarkar
2020-03-28 6:34 ` [PATCH 2/2] iio: imu: adis16460: " Rohit Sarkar
2020-03-29 9:38 ` [PATCH 0/2] " Jonathan Cameron
2020-03-29 11:34 ` Rohit Sarkar
2020-03-29 13:46 ` Lars-Peter Clausen
2020-03-29 15:39 ` Rohit Sarkar
2020-03-30 9:20 ` Ardelean, Alexandru
2020-03-31 10:58 ` Sa, Nuno
2020-03-31 11:08 ` Lars-Peter Clausen
2020-03-31 11:19 ` Rohit Sarkar
2020-03-31 11:49 ` Rohit Sarkar [this message]
2020-03-31 15:30 ` Sa, Nuno
2020-03-31 11:47 ` [PATCH v2 " Rohit Sarkar
2020-03-31 11:47 ` [PATCH v2 1/2] iio: imu: adis16400: " Rohit Sarkar
2020-03-31 15:28 ` Sa, Nuno
2020-04-04 15:32 ` Jonathan Cameron
2020-03-31 11:47 ` [PATCH v2 2/2] iio: imu: adis16460: " Rohit Sarkar
2020-03-31 15:28 ` Sa, Nuno
2020-04-04 15:34 ` Jonathan Cameron
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=5e832e62.1c69fb81.2a0e9.b85d@mx.google.com \
--to=rohitsarkar5398@gmail.com \
--cc=Dragos.Bogdan@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=Nuno.Sa@analog.com \
--cc=alexandru.Ardelean@analog.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=stefan.popa@analog.com \
--cc=zhongjiang@huawei.com \
/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).