From: "Denis V. Lunev" <den@openvz.org>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Netdev List <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 2/2] iwlwifi: small compile warnings without CONFIG_IWLWIFI_DEBUG
Date: Thu, 17 Jul 2008 19:05:06 +0400 [thread overview]
Message-ID: <1216307106.7034.15.camel@iris.sw.ru> (raw)
In-Reply-To: <1ba2fa240807170437j12547b26l803551b61a805f8d@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 325 bytes --]
> > If you agree with this, I'll resend the patch with
> > iwl_rx_scan_results_notif modified.
>
> Anyhow please send the patch only for scanning. I will apply the rs
> portion on our new code, which is still not visible...just to avoid
> conflict. I will keep your credit
> Thanks
> Tomas
could I have your ack for this?
[-- Attachment #2: 0002-iwlwifi-small-compile-warnings-without-CONFIG_IWLWI.patch --]
[-- Type: application/mbox, Size: 1503 bytes --]
next prev parent reply other threads:[~2008-07-17 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 9:19 [PATCH net-next 1/2] iwlwifi: compilation error when CONFIG_IWLWIFI_DEBUG is not set Denis V. Lunev
[not found] ` <1216286365-11703-1-git-send-email-den-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-07-17 9:19 ` [PATCH net-next 2/2] iwlwifi: small compile warnings without CONFIG_IWLWIFI_DEBUG Denis V. Lunev
2008-07-17 11:08 ` Tomas Winkler
[not found] ` <1ba2fa240807170408w13837d67hcfd1be50fdb07738-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-17 11:26 ` Denis V. Lunev
[not found] ` <1ba2fa240807170437j12547b26l803551b61a805f8d@mail.gmail.com>
2008-07-17 15:05 ` Denis V. Lunev [this message]
[not found] ` <1216307106.7034.15.camel-aPCOdVxUTlgvJsYlp49lxw@public.gmane.org>
2008-07-17 15:26 ` Tomas Winkler
2008-07-18 6:56 ` [PATCH net-next 2/2][v2] " Denis V. Lunev
2008-07-17 11:05 ` [PATCH net-next 1/2] iwlwifi: compilation error when CONFIG_IWLWIFI_DEBUG is not set Tomas Winkler
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=1216307106.7034.15.camel@iris.sw.ru \
--to=den@openvz.org \
--cc=netdev@vger.kernel.org \
--cc=tomasw@gmail.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).