From: "John W. Linville" <linville@tuxdriver.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net
Subject: Re: [PATCH 2/3] ath: use seq_file api for ath9k debugfs files
Date: Fri, 31 Oct 2014 16:07:04 -0400 [thread overview]
Message-ID: <20141031200704.GE3768@tuxdriver.com> (raw)
In-Reply-To: <1414498752-9746-3-git-send-email-arend@broadcom.com>
On Tue, Oct 28, 2014 at 01:19:11PM +0100, Arend van Spriel wrote:
> The debugfs files that are defined in debug.c which are read-only
> and using a simple_open as .open file operation have been modified
> to use the single_open seq_file API. This simplifies the read
> functions defining the file contents.
>
> Signed-off-by: Arend van Spriel <arend@broadcom.com>
Acked-by: John W. Linville <linville@tuxdriver.com>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2014-10-31 20:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 12:19 [PATCH 0/3] debugfs: adding helper for single seq_file Arend van Spriel
2014-10-28 12:19 ` [PATCH 1/3] debugfs: add helper function to create device related seq_file Arend van Spriel
2014-11-07 19:04 ` Greg Kroah-Hartman
2014-10-28 12:19 ` [PATCH 2/3] ath: use seq_file api for ath9k debugfs files Arend van Spriel
2014-10-31 20:07 ` John W. Linville [this message]
2014-11-07 19:05 ` Greg Kroah-Hartman
2014-11-08 13:44 ` Arend van Spriel
2014-11-08 14:07 ` Arend van Spriel
2014-11-08 16:25 ` Greg Kroah-Hartman
2014-10-28 12:19 ` [PATCH 3/3] ath: ath9k: use debugfs_create_devm_seqfile() helper for seq_file entries Arend van Spriel
2014-10-31 20:07 ` John W. Linville
2014-11-07 19:05 ` Greg Kroah-Hartman
2014-10-30 19:19 ` [PATCH 0/3] debugfs: adding helper for single seq_file John W. Linville
2014-10-30 19:39 ` Greg Kroah-Hartman
2014-10-30 19:48 ` Arend van Spriel
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=20141031200704.GE3768@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=arend@broadcom.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-wireless@vger.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;
as well as URLs for NNTP newsgroup(s).