Search Linux Wireless

Re: [PATCH 2/3] ath: use seq_file api for ath9k debugfs files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxx>
> >>>Acked-by: John W. Linville<linville@xxxxxxxxxxxxx>
> >>>---
> >>>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
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux