From: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
To: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Cc: "John W . Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>,
Joe Perches <joe@perches.com>, <linux-wireless@vger.kernel.org>,
"Luis R . Rodriguez" <rodrigue@qca.qualcomm.com>
Subject: Re: [PATCH v10 2/3] wil6210: Local compensation for dynamic hexdump
Date: Wed, 12 Dec 2012 07:56:10 -0800 [thread overview]
Message-ID: <20121212155610.GK15974@pogo> (raw)
In-Reply-To: <1355327278-12965-3-git-send-email-qca_vkondrat@qca.qualcomm.com>
On Wed, Dec 12, 2012 at 05:47:57PM +0200, Vladimir Kondratiev wrote:
> Unless patch for dynamic hexdump merged into mainstream kernel,
> need to provide replacement for the dynamic hexdump functionality
>
> This patch do not hurt compilation with kernel that have
> 'dynamic hexdump' patch merged - check performed by
> #if !defined(print_hex_dump_debug)
>
> To REMOVE when dynamic hexdump merged!!
>
> Signed-off-by: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
I'd say just prefix with wil_ for now.
Luis
next prev parent reply other threads:[~2012-12-12 15:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 15:47 [PATCH v10 0/3] wireless: Driver for 60GHz card wil6210 Vladimir Kondratiev
2012-12-12 15:47 ` [PATCH v10 1/3] " Vladimir Kondratiev
2012-12-12 15:47 ` [PATCH v10 2/3] wil6210: Local compensation for dynamic hexdump Vladimir Kondratiev
2012-12-12 15:56 ` Luis R. Rodriguez [this message]
2012-12-13 7:45 ` [PATCH] wil6210: alternative functions " Vladimir Kondratiev
2012-12-12 15:47 ` [PATCH v10 3/3] wireless: integrate wil6210 driver into build Vladimir Kondratiev
2012-12-12 16:04 ` [PATCH v10 0/3] wireless: Driver for 60GHz card wil6210 Johannes Berg
2012-12-12 16:25 ` Vladimir Kondratiev
2012-12-13 20:51 ` Luis R. Rodriguez
2012-12-16 12:29 ` [PATCH v11] " Vladimir Kondratiev
2012-12-19 7:55 ` Vladimir Kondratiev
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=20121212155610.GK15974@pogo \
--to=rodrigue@qca.qualcomm.com \
--cc=joe@perches.com \
--cc=johannes@sipsolutions.net \
--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).