From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Arend van Spriel <arend@broadcom.com>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org
Subject: Re: [PATCH 2/3] ath: use seq_file api for ath9k debugfs files
Date: Sat, 8 Nov 2014 08:25:17 -0800 [thread overview]
Message-ID: <20141108162517.GA16580@kroah.com> (raw)
In-Reply-To: <545E23B6.1060004@broadcom.com>
On Sat, Nov 08, 2014 at 03:07:50PM +0100, Arend van Spriel wrote:
> On 11/08/14 14:44, Arend van Spriel wrote:
> >On 11/07/14 20:05, Greg Kroah-Hartman wrote:
> >>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>
> >>>---
> >>>drivers/net/wireless/ath/ath9k/debug.c | 425
> >>>+++++++++++++--------------------
> >>>drivers/net/wireless/ath/ath9k/debug.h | 3 +-
> >>>2 files changed, 173 insertions(+), 255 deletions(-)
> >>
> >>I can't take patch 1/3 right now, but even if I could, this one doesn't
> >>apply to 3.18-rc3 :(
>
> driver-core/driver-core-next branch is not on 3.18-rc3.
Yes it is based on that branch. Why do you think it isn't?
> Should I rebase the series on driver-core/master?
No, that's a "clean" 3.18-rc3, which doesn't include any patches that
I've accepted so far for 3.19.
> As this is for 3.19 I figured it needed to go on some -next branch.
Yes, if you make it against driver-core-next that is fine, please do so.
thanks,
greg k-h
next prev parent reply other threads:[~2014-11-08 16:26 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
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 [this message]
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=20141108162517.GA16580@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arend@broadcom.com \
--cc=ath9k-devel@lists.ath9k.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).