linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
To: Joe Perches <joe@perches.com>
Cc: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	Jason Baron <jbaron@redhat.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	<linux-wireless@vger.kernel.org>,
	Jim Cromie <jim.cromie@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] dynamic_debug: introduce debug_hex_dump()
Date: Tue, 11 Dec 2012 14:55:55 -0800	[thread overview]
Message-ID: <20121211225555.GC15974@pogo> (raw)
In-Reply-To: <1355257444.24219.7.camel@joe-AO722>

On Tue, Dec 11, 2012 at 12:24:04PM -0800, Joe Perches wrote:
> On Tue, 2012-12-11 at 12:12 -0800, Greg KH wrote:
> > On Tue, Dec 11, 2012 at 03:08:31PM -0500, Jason Baron wrote:
> > > On Tue, Dec 11, 2012 at 11:36:46AM -0800, Luis R. Rodriguez wrote:
> > > > On Tue, Dec 04, 2012 at 11:28:26AM +0200, Vladimir Kondratiev wrote:
> > > > > Hi Jason,
> > > > > 
> > > > > Do you have any update on the status for patches below?
> > > > > Where is it now? When do you expect it to merge? 3.8?
> > > > > I am waiting for this to merge before I can go on
> > > > > with my driver.
> > > > 
> > > > *poke*
> > > > 
> > > >   Luis
> > > 
> > > Hi Luis,
> > > 
> > > Yes, I posted this patch, along with 2 others last week for Greg to
> > > pull. I believe these are too late for the 3.8 merge window. Perhaps,
> > > Greg can comment. Here's a link to the post:
> > > 
> > > http://marc.info/?l=linux-kernel&m=135474417810281&w=2
> > 
> > Yes it's too late, these will go into linux-next after 3.8-rc1 is out.
> > 
> > thanks,
> > 
> > greg k-h
> > 
> 
> Vladimir, sorry about this.
> 
> I suggest you prefix/rename and include these functions directly into
> your driver and later after 3.9 is out you could again rename the
> local calls to the now generic kernel functions and delete the local
> ones.

Vladimir, to be clear, you can continue with waiting for the patches
to get into 3.9 but that will take a while but given that you want
your driver in 3.8 you can fold those routines into your driver as
you had before but with a rename by adding a prefix and sumbit that
driver and specify it is for 3.8.

> Your driver is for new hardware, so even now it should be able to
> go into 3.8.

Agreed.

  Luis

  reply	other threads:[~2012-12-11 22:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14 12:17 [RFC] debug_hex_dump() Vladimir Kondratiev
2012-11-14 12:17 ` [RFC] dynamic_debug: introduce debug_hex_dump() Vladimir Kondratiev
2012-11-14 13:41   ` Joe Perches
2012-11-14 16:18     ` Vladimir Kondratiev
2012-11-14 17:08       ` Joe Perches
2012-11-14 17:27         ` Vladimir Kondratiev
     [not found]           ` <3304277.iqgq3GH3Yo@lx-vladimir>
2012-11-18 13:51             ` Vladimir Kondratiev
2012-11-18 13:55               ` [PATCH 2/2] dynamic_debug: use constant format in print_hex_dump_bytes() Vladimir Kondratiev
2012-11-18 13:57               ` [PATCH 1/2] dynamic_debug: dynamic hex dump Vladimir Kondratiev
2012-11-18 14:38             ` [RFC] dynamic_debug: introduce debug_hex_dump() Joe Perches
2012-11-18 15:43               ` Vladimir Kondratiev
2012-11-18 17:01                 ` Vladimir Kondratiev
2012-11-18 18:35                   ` Joe Perches
2012-11-20 16:08                     ` Jason Baron
2012-12-04  9:28                       ` Vladimir Kondratiev
2012-12-11 19:36                         ` Luis R. Rodriguez
2012-12-11 20:08                           ` Jason Baron
2012-12-11 20:12                             ` Greg KH
2012-12-11 20:24                               ` Joe Perches
2012-12-11 22:55                                 ` Luis R. Rodriguez [this message]
2012-12-12  9:12                                   ` Vladimir Kondratiev
2012-12-12 15:41                                     ` Luis R. Rodriguez

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=20121211225555.GC15974@pogo \
    --to=rodrigue@qca.qualcomm.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jbaron@redhat.com \
    --cc=jim.cromie@gmail.com \
    --cc=joe@perches.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=qca_vkondrat@qca.qualcomm.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).