From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail.linuxfoundation.org ([140.211.169.12]:49447 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753725AbaKHQ0c (ORCPT ); Sat, 8 Nov 2014 11:26:32 -0500 Date: Sat, 8 Nov 2014 08:25:17 -0800 From: Greg Kroah-Hartman To: Arend van Spriel 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 Message-ID: <20141108162517.GA16580@kroah.com> (sfid-20141108_172940_945522_19007F21) References: <1414498752-9746-1-git-send-email-arend@broadcom.com> <1414498752-9746-3-git-send-email-arend@broadcom.com> <20141107190522.GA4694@kroah.com> <545E1E45.9040204@broadcom.com> <545E23B6.1060004@broadcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <545E23B6.1060004@broadcom.com> Sender: linux-wireless-owner@vger.kernel.org List-ID: 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 > >>>Acked-by: John W. Linville > >>>--- > >>>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