All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kbuild test robot <fengguang.wu@intel.com>,
	kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: wilc_wfi_cfgoperations.c:undefined reference to `cfg80211_ready_on_channel'
Date: Sun, 22 Nov 2015 17:41:12 -0800	[thread overview]
Message-ID: <20151123014112.GA10256@kroah.com> (raw)
In-Reply-To: <6928786.slL562UaMV@wuerfel>

On Sun, Nov 22, 2015 at 11:31:00PM +0100, Arnd Bergmann wrote:
> On Sunday 22 November 2015 13:53:44 kbuild test robot wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head:   3ad5d7e06a96d54a55acb5ab25938a06814605c8
> > commit: bcc43a4b5ed75285aeacf2cf8d9b96d6379fb429 staging/wilc: fix Kconfig dependencies, second try
> > date:   5 weeks ago
> > config: i386-randconfig-x0-11221258 (attached as .config)
> > reproduce:
> >         git checkout bcc43a4b5ed75285aeacf2cf8d9b96d6379fb429
> >         # save the attached .config to linux build tree
> >         make ARCH=i386 
> 
> It's a known problem, I've sent a longish series to address this properly
> as well as fix a number of other problems I found on the way.
> 
> I could make a simpler fix for v4.4 we want this problem solved in
> the longterm kernel without needing to pull in my longer series that
> now depends on other patches from staging-testing.

Don't worry about staging drivers for "longterm" kernels, no distros
enable them so it's not a big deal, especially for "embedded" hardware
like this one.

thanks,

greg k-h

      reply	other threads:[~2015-11-23  1:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-22  5:53 wilc_wfi_cfgoperations.c:undefined reference to `cfg80211_ready_on_channel' kbuild test robot
2015-11-22 22:31 ` Arnd Bergmann
2015-11-23  1:41   ` Greg Kroah-Hartman [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=20151123014112.GA10256@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.