netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: linville@tuxdriver.com
Cc: David Miller <davem@davemloft.net>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: pull request: wireless-next-2.6 2009-06-04
Date: Sun, 07 Jun 2009 16:18:41 +0200	[thread overview]
Message-ID: <4A2BCC41.1060508@hartkopp.net> (raw)
In-Reply-To: <20090607.033751.191866033.davem@davemloft.net>

David Miller wrote:
> From: "John W. Linville" <linville@tuxdriver.com>
> Date: Thu, 4 Jun 2009 11:20:11 -0400
> 
>> Hopefully this is (almost?) the last wireless pull request for
>> non-bugfix patches intended for 2.6.31...
>>

(..)

>>
>> Please let me know if there are problems!
> 
> Pulled into net-next-2.6 and I'll push it back out to kernel.org
> after some build testing.

Hi John,

after pulling the latest net-next-2.6 i got this warning which is probably
caused by CONFIG_RFKILL=m in my config:

hartko@vwagwolkf320:~/net-next-2.6$ make oldconfig
scripts/kconfig/conf -o arch/x86/Kconfig
.config:614:warning: symbol value 'm' invalid for RFKILL_INPUT
*
* Restart config...
*
*
* RF switch subsystem support
*
RF switch subsystem support (RFKILL) [M/n/y/?] m
  RF switch input support (RFKILL_INPUT) [Y/n] (NEW)
#
# configuration written to .config
#
hartko@vwagwolkf320:~/net-next-2.6$ make -j2
scripts/kconfig/conf -s arch/x86/Kconfig
include/config/auto.conf:578:warning: symbol value 'm' invalid for RFKILL_INPUT
  CHK     include/linux/version.h
  CHK     include/linux/utsrelease.h
  UPD     include/linux/utsrelease.h
...

Regards,
Oliver


  reply	other threads:[~2009-06-07 14:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04 15:20 pull request: wireless-next-2.6 2009-06-04 John W. Linville
2009-06-07 10:37 ` David Miller
2009-06-07 14:18   ` Oliver Hartkopp [this message]
2009-06-07 14:58     ` John W. Linville
     [not found]       ` <20090607145830.GA2736-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2009-06-07 15:04         ` Oliver Hartkopp
2009-06-07 15:11         ` Oliver Hartkopp
2009-06-07 15:26           ` John W. Linville
     [not found]           ` <4A2BD8A5.4040302-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2009-06-07 15:29             ` Marcel Holtmann
     [not found]               ` <1244388583.23850.87.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-06-14  8:54                 ` rfkill regression in net-next-2.6 Oliver Hartkopp
     [not found]                   ` <4A34BAB9.9000104-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2009-06-14  9:17                     ` Oliver Hartkopp
2009-06-15 12:04                     ` John W. Linville
     [not found]                       ` <20090615120422.GA2729-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2009-06-15 12:24                         ` Johannes Berg
2009-06-15 13:20                           ` 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=4A2BCC41.1060508@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=davem@davemloft.net \
    --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).