From: "Sa, Nuno" <Nuno.Sa@analog.com>
To: "jic23@kernel.org" <jic23@kernel.org>
Cc: "Hennerich, Michael" <Michael.Hennerich@analog.com>,
"lars@metafoo.de" <lars@metafoo.de>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"pmeerw@pmeerw.net" <pmeerw@pmeerw.net>,
"knaack.h@gmx.de" <knaack.h@gmx.de>
Subject: Re: [PATCH 2/2] iio: adis16480: Add debugfs_reg_access entry
Date: Mon, 28 Oct 2019 08:25:24 +0000 [thread overview]
Message-ID: <5a01de12c49f198d6d09b5e733225c6cc357f822.camel@analog.com> (raw)
In-Reply-To: <20191027163700.16d7d3f8@archlinux>
On Sun, 2019-10-27 at 16:37 +0000, Jonathan Cameron wrote:
> On Fri, 25 Oct 2019 14:45:08 +0200
> Nuno Sá <nuno.sa@analog.com> wrote:
>
> > The driver is defining debugfs entries by calling
> > `adis16480_debugfs_init()`. However, those entries are attached to
> > the
> > iio_dev debugfs entry which won't exist if no debugfs_reg_access
> > callback is provided.
> >
> > Signed-off-by: Nuno Sá <nuno.sa@analog.com>
> As you are respinning the first one and this is probably stable
> material as well, please add a fixes tag for v2.
> Thanks,
>
Will do that. Should I also cc Stable?
Thanks!
Nuno Sá
next prev parent reply other threads:[~2019-10-28 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 12:45 [PATCH 1/2] iio: adis16480: Fix scales factors Nuno Sá
2019-10-25 12:45 ` [PATCH 2/2] iio: adis16480: Add debugfs_reg_access entry Nuno Sá
2019-10-27 16:37 ` Jonathan Cameron
2019-10-28 8:25 ` Sa, Nuno [this message]
2019-10-29 18:25 ` Jonathan Cameron
2019-10-30 7:53 ` Sa, Nuno
2019-10-27 16:24 ` [PATCH 1/2] iio: adis16480: Fix scales factors 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=5a01de12c49f198d6d09b5e733225c6cc357f822.camel@analog.com \
--to=nuno.sa@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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).