From: David Miller <davem@davemloft.net>
To: meenakshi.venkataraman@intel.com
Cc: socketcan@hartkopp.net, wey-yi.w.guy@intel.com,
linville@tuxdriver.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, david.spinadel@intel.com
Subject: Re: net-next iwlwifi breaks compile - was Re: pull request: wireless-next 2012-04-18
Date: Thu, 19 Apr 2012 15:49:54 -0400 (EDT) [thread overview]
Message-ID: <20120419.154954.1322943404183128381.davem@davemloft.net> (raw)
In-Reply-To: <4595B4D22AB93C4FABBA84AAD5AA37FD1258AA@ORSMSX103.amr.corp.intel.com>
From: "Venkataraman, Meenakshi" <meenakshi.venkataraman@intel.com>
Date: Thu, 19 Apr 2012 19:47:58 +0000
> It was fixed internally in a subsequent patch, but that patch has
> not made it into net-next. I don't see it in the public iwlwifi
> repository either. We'll add the fix to the repository so you can
> pick it up.
That's not how this works.
You should submit a patch to fix the build directly to me, immediately,
so that I can push it directly into net-next as fast as possible.
next prev parent reply other threads:[~2012-04-19 19:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 19:05 pull request: wireless-next 2012-04-18 John W. Linville
2012-04-18 19:36 ` David Miller
[not found] ` <20120418.153653.2130740499995307564.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2012-04-19 4:49 ` net-next iwlwifi breaks compile - was " Oliver Hartkopp
[not found] ` <4F8F9977.9040703-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2012-04-19 19:47 ` Venkataraman, Meenakshi
2012-04-19 19:49 ` David Miller [this message]
[not found] ` <20120419.154954.1322943404183128381.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2012-04-19 20:10 ` Guy, Wey-Yi
2012-04-19 20:27 ` David Miller
2012-04-19 21:07 ` Venkataraman, Meenakshi
[not found] ` <4595B4D22AB93C4FABBA84AAD5AA37FD1259E6-P5GAC/sN6hlQxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-04-20 5:18 ` Oliver Hartkopp
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=20120419.154954.1322943404183128381.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=david.spinadel@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=meenakshi.venkataraman@intel.com \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=wey-yi.w.guy@intel.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).