From: Alexander Beregalov <a.beregalov@gmail•com>
To: Sachin Sant <sachinp@in•ibm.com>,
Larry Finger <Larry.Finger@lwfinger•net>,
linux-wireless@vger•kernel.org
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
netdev <netdev@vger•kernel.org>
Subject: Re: April 22 Next : net/rfkill randconfig failure
Date: Thu, 23 Apr 2009 13:54:24 +0400 [thread overview]
Message-ID: <a4423d670904230254v672798ddtda443e549ef45490@mail.gmail.com> (raw)
In-Reply-To: <49EEF38D.8000801@in.ibm.com>
2009/4/22 Sachin Sant <sachinp@in•ibm.com>:
> Today's next tree build (x86 randconfig) failed with
>
> net/rfkill/rfkill.c: In function 'update_rfkill_state':
> net/rfkill/rfkill.c:99: error: implicit declaration of function
> 'rfkill_led_trigger'
> make[2]: *** [net/rfkill/rfkill.o] Error 1
>
> .config attached
>
Add CCs
next prev parent reply other threads:[~2009-04-23 9:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 5:42 linux-next: Tree for April 22 Stephen Rothwell
2009-04-22 8:41 ` linux-next: Tree for April 22 [BUG] ep93xx_keypad_open: undefined reference to `clk_set_rate' Matthias Kaehlcke
2009-04-22 16:55 ` linux-next: Tree for April 22 [BUG] ep93xx_keypad_open:undefined " H Hartley Sweeten
2009-04-22 10:38 ` April 22 Next : net/rfkill randconfig failure Sachin Sant
2009-04-23 9:54 ` Alexander Beregalov [this message]
2009-04-23 10:33 ` Ken Lewis
2009-04-22 12:49 ` linux-next: Tree for April 22: kmemleak: unreferenced object Matthias Kaehlcke
2009-04-23 11:01 ` Catalin Marinas
2009-04-22 16:53 ` linux-next: Tree for April 22 (rndis_wlan) Randy Dunlap
[not found] ` <49EF4B73.2050702-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-04-22 17:28 ` John W. Linville
2009-04-22 19:06 ` Randy Dunlap
[not found] ` <20090422172804.GE3288-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2009-04-22 21:08 ` Jussi Kivilinna
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=a4423d670904230254v672798ddtda443e549ef45490@mail.gmail.com \
--to=a.beregalov@gmail$(echo .)com \
--cc=Larry.Finger@lwfinger$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sachinp@in$(echo .)ibm.com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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