From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org,
Michael Jamet <michael.jamet@intel.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
Andreas Noever <andreas.noever@gmail.com>,
Gil Fine <gil.fine@intel.com>, Lukas Wunner <lukas@wunner.de>
Subject: Re: [PATCH 9/9] thunderbolt: Add debugfs interface
Date: Wed, 26 Aug 2020 14:40:52 +0300 [thread overview]
Message-ID: <20200826114052.GK1375436@lahna.fi.intel.com> (raw)
In-Reply-To: <20200826112246.GA3760307@kroah.com>
Hi Greg,
On Wed, Aug 26, 2020 at 01:22:46PM +0200, Greg Kroah-Hartman wrote:
> > +#define DEBUGFS_ATTR(__space, __write) \
> > +static int __space ## _open(struct inode *inode, struct file *file) \
> > +{ \
> > + return single_open(file, __space ## _show, inode->i_private); \
> > +} \
> > + \
> > +static const struct file_operations __space ## _fops = { \
> > + .owner = THIS_MODULE, \
> > + .open = __space ## _open, \
> > + .release = single_release, \
> > + .read = seq_read, \
> > + .write = __write, \
> > + .llseek = seq_lseek, \
> > +}
> > +
> > +#define DEBUGFS_ATTR_RO(__space) \
> > + DEBUGFS_ATTR(__space, NULL)
> > +
> > +#define DEBUGFS_ATTR_RW(__space) \
> > + DEBUGFS_ATTR(__space, __space ## _write)
>
> We do have DEFINE_SIMPLE_ATTRIBUTE() and DEFINE_DEBUGFS_ATTRIBUTE, do
> those work here instead of your custom macro?
Unfortunately they do not work as they want u64 for the write side but
we actually need to parse (offset, value) pairs here when write is
enabled.
> Other than that, this series looks fine to me:
>
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Thanks!
next prev parent reply other threads:[~2020-08-26 11:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 11:07 [PATCH 0/9] thunderbolt: Add debugfs support Mika Westerberg
2020-08-26 11:07 ` [PATCH 1/9] thunderbolt: Move struct tb_cap_any to tb_regs.h Mika Westerberg
2020-08-26 11:07 ` [PATCH 2/9] thunderbolt: Introduce tb_port_next_cap() Mika Westerberg
2020-08-26 11:07 ` [PATCH 3/9] thunderbolt: Introduce tb_switch_next_cap() Mika Westerberg
2020-09-01 9:01 ` [PATCH v2 " Mika Westerberg
2020-08-26 11:07 ` [PATCH 4/9] thunderbolt: Introduce tb_port_is_nhi() Mika Westerberg
2020-08-26 11:07 ` [PATCH 5/9] thunderbolt: Check for Intel vendor ID when identifying controller Mika Westerberg
2020-08-26 11:07 ` [PATCH 6/9] thunderbolt: Introduce tb_switch_is_ice_lake() Mika Westerberg
2020-08-26 11:07 ` [PATCH 7/9] thunderbolt: Introduce tb_switch_is_tiger_lake() Mika Westerberg
2020-08-26 11:07 ` [PATCH 8/9] thunderbolt: No need to warn in TB_CFG_ERROR_INVALID_CONFIG_SPACE Mika Westerberg
2020-08-26 11:07 ` [PATCH 9/9] thunderbolt: Add debugfs interface Mika Westerberg
2020-08-26 11:22 ` Greg Kroah-Hartman
2020-08-26 11:40 ` Mika Westerberg [this message]
2020-09-03 9:27 ` [PATCH 0/9] thunderbolt: Add debugfs support Mika Westerberg
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=20200826114052.GK1375436@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=gil.fine@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=michael.jamet@intel.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).