From: "Sharma, Sanjeev" <Sanjeev_Sharma@mentor.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "dsd@gentoo.org" <dsd@gentoo.org>,
"kune@deine-taler.de" <kune@deine-taler.de>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] zd1211rw: replace ZD_ASSERT with lockdep_assert_held()
Date: Fri, 22 Aug 2014 11:40:15 +0000 [thread overview]
Message-ID: <FDC088D3B5555644AE135ED28A7ABDE94DF3165A@EU-MBX-02.mgc.mentorg.com> (raw)
In-Reply-To: <1408707084.4349.0.camel@jlt4.sipsolutions.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 679 bytes --]
Yes, it compiling successfully.
-----Original Message-----
From: Johannes Berg [mailto:johannes@sipsolutions.net]
Sent: Friday, August 22, 2014 5:01 PM
To: Sharma, Sanjeev
Cc: dsd@gentoo.org; kune@deine-taler.de; linville@tuxdriver.com; linux-wireless@vger.kernel.org; netdev@vger.kernel.org; linux-kernel@vger.kernel.org
Subject: Re: [PATCH] zd1211rw: replace ZD_ASSERT with lockdep_assert_held()
On Tue, 2014-08-19 at 06:39 +0000, Sharma, Sanjeev wrote:
> Ping for review the patch.
Make sure it compiles ...
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2014-08-22 11:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 7:05 [PATCH] zd1211rw: replace ZD_ASSERT with lockdep_assert_held() Sanjeev Sharma
2014-08-19 6:39 ` Sharma, Sanjeev
2014-08-22 11:31 ` Johannes Berg
2014-08-22 11:40 ` Sharma, Sanjeev [this message]
2014-09-11 4:02 ` Sharma, Sanjeev
2014-09-11 6:53 ` Johannes Berg
2014-09-11 10:09 ` [PATCH v2] " Sanjeev Sharma
2014-09-11 10:12 ` Johannes Berg
2014-09-11 10:36 ` Sharma, Sanjeev
2014-09-11 10:42 ` Johannes Berg
2014-09-15 6:02 ` Julian Calaby
2014-09-30 7:42 ` Sharma, Sanjeev
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=FDC088D3B5555644AE135ED28A7ABDE94DF3165A@EU-MBX-02.mgc.mentorg.com \
--to=sanjeev_sharma@mentor.com \
--cc=dsd@gentoo.org \
--cc=johannes@sipsolutions.net \
--cc=kune@deine-taler.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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).