From: Oliver Hartkopp <socketcan@hartkopp.net>
To: "Venkataraman, Meenakshi" <meenakshi.venkataraman@intel.com>
Cc: David Miller <davem@davemloft.net>,
"Guy, Wey-Yi W" <wey-yi.w.guy@intel.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Spinadel, David" <david.spinadel@intel.com>
Subject: Re: net-next iwlwifi breaks compile - was Re: pull request: wireless-next 2012-04-18
Date: Fri, 20 Apr 2012 07:18:59 +0200 [thread overview]
Message-ID: <4F90F1C3.8020604@hartkopp.net> (raw)
In-Reply-To: <4595B4D22AB93C4FABBA84AAD5AA37FD1259E6@ORSMSX103.amr.corp.intel.com>
Thanks guys!
I just pulled net-next and it's compiling properly now.
Regards,
Oliver
On 19.04.2012 23:07, Venkataraman, Meenakshi wrote:
> Hi David,
>
>>> 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.
>
> [MV] Okay -- this is good to know. Essentially -- if any upstream tree breaks due to our work, then a fix should be directly submitted ASAP to the maintainer of that tree.
>
> I see that Wey-Yi has already sent you the fix, so nothing left for me to do on this one.
>
> Thanks,
> Meenakshi
prev parent reply other threads:[~2012-04-20 5:19 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
2012-04-19 4:49 ` net-next iwlwifi breaks compile - was " Oliver Hartkopp
2012-04-19 19:47 ` Venkataraman, Meenakshi
2012-04-19 19:49 ` David Miller
2012-04-19 20:10 ` Guy, Wey-Yi
2012-04-19 20:27 ` David Miller
2012-04-19 21:07 ` Venkataraman, Meenakshi
2012-04-20 5:18 ` Oliver Hartkopp [this message]
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=4F90F1C3.8020604@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=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=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).