linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-wireless <linux-wireless@vger.kernel.org>,
	linux-next@vger.kernel.org, sfr@canb.auug.org.au, mhocko@suse.cz,
	ath9k-devel@lists.ath9k.org
Subject: Re: mmotm 2014-11-12-16-34 uploaded (net/wireless/ath9k)
Date: Thu, 13 Nov 2014 09:29:53 -0800	[thread overview]
Message-ID: <5464EA91.60409@infradead.org> (raw)
In-Reply-To: <5463fd01.PiBwUnCphi1MBsM6%akpm@linux-foundation.org>

On 11/12/14 16:36, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2014-11-12-16-34 has been uploaded to
> 
>    http://www.ozlabs.org/~akpm/mmotm/
> 
> mmotm-readme.txt says
> 
> README for mm-of-the-moment:
> 
> http://www.ozlabs.org/~akpm/mmotm/
> 

on x86_64: (from linux-next.patch, not mmotm patches)


  CC [M]  drivers/net/wireless/ath/ath9k/common-spectral.o
../drivers/net/wireless/ath/ath9k/common-spectral.c:40:5: error: redefinition of 'ath_cmn_process_fft'
 int ath_cmn_process_fft(struct ath_spec_scan_priv *spec_priv, struct ieee80211_hdr *hdr,
     ^
In file included from ../drivers/net/wireless/ath/ath9k/common.h:27:0,
                 from ../drivers/net/wireless/ath/ath9k/ath9k.h:27,
                 from ../drivers/net/wireless/ath/ath9k/common-spectral.c:18:
../drivers/net/wireless/ath/ath9k/common-spectral.h:146:19: note: previous definition of 'ath_cmn_process_fft' was here
 static inline int ath_cmn_process_fft(struct ath_spec_scan_priv *spec_priv,
                   ^
make[6]: *** [drivers/net/wireless/ath/ath9k/common-spectral.o] Error 1



-- 
~Randy

           reply	other threads:[~2014-11-13 17:30 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <5463fd01.PiBwUnCphi1MBsM6%akpm@linux-foundation.org>]

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=5464EA91.60409@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=sfr@canb.auug.org.au \
    /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).