linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@qca.qualcomm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Zefir Kurtisi <zefir.kurtisi@neratec.com>
Subject: Re: linux-next: build failure after merge of the wireless-next tree
Date: Mon, 19 Dec 2011 18:42:02 -0800	[thread overview]
Message-ID: <CAB=NE6V12m2_u6YGxhmqjNGs9OjdOKFpCAYu5cs_Hezwwk9LLA@mail.gmail.com> (raw)
In-Reply-To: <20111220131802.e3782dfbf8172281a7df5a5c@canb.auug.org.au>

On Mon, Dec 19, 2011 at 6:18 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi John,
>
> After merging the wireless-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/net/wireless/ath/ath9k/dfs.c: In function 'ath9k_postprocess_radar_event':
> drivers/net/wireless/ath/ath9k/dfs.c:73:1: error: 'ATH_DBG_ATH_DBG_DFS' undeclared (first use in this function)
> drivers/net/wireless/ath/ath9k/dfs.c: In function 'ath9k_dfs_process_phyerr':
> drivers/net/wireless/ath/ath9k/dfs.c:166:1: error: 'ATH_DBG_ATH_DBG_DFS' undeclared (first use in this function)
>
> Caused by commit 29942bc12537 ("ath9k: add DFS radar pulse processing").
> ath_dbg prepends ATH_DBG_ to its second argument.
>
> I have used the wireless-next tree from next-20111219 for today.

Odd, gitweb for wireless-next.git shows only one commit to dfs.c, the
change that introduced it:

http://git.kernel.org/?p=linux/kernel/git/linville/wireless-next.git;a=history;f=drivers/net/wireless/ath/ath9k/dfs.c;h=e4e84a9e62730f3780a7eda6b4b00d535dd1d428;hb=HEAD

In that version of the file I see nothing with ATH_DBG_ATH_DBG_DFS. I
also do not see it on wireless-testing.

mcgrof@tux ~/wireless-testing (git::master)$ git show 29942bc12537 |
grep ATH_DBG_ATH_DBG_DFS

  Luis

  reply	other threads:[~2011-12-20  2:42 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20  2:18 linux-next: build failure after merge of the wireless-next tree Stephen Rothwell
2011-12-20  2:42 ` Luis R. Rodriguez [this message]
2011-12-20  2:57   ` Stephen Rothwell
2011-12-20  3:24     ` Luis R. Rodriguez
  -- strict thread matches above, loose matches on Subject: below --
2014-09-08  8:42 Stephen Rothwell
2014-09-09 23:28 ` Stephen Rothwell
2014-09-09 23:37   ` David Miller
2014-09-10 17:46     ` John W. Linville
2014-07-16  3:28 Stephen Rothwell
2014-07-16 14:09 ` John W. Linville
2014-04-23  3:47 Stephen Rothwell
2014-04-23 20:54 ` Bing Zhao
2014-03-06  2:43 Stephen Rothwell
2014-03-06  8:53 ` Arend van Spriel
2014-03-06  2:24 Stephen Rothwell
2014-02-25  2:35 Stephen Rothwell
2014-02-25 19:07 ` John W. Linville
2014-02-25 20:47   ` Stephen Rothwell
2014-03-04 23:16     ` Stephen Rothwell
2014-03-04 23:21       ` Stephen Rothwell
2014-03-04 23:49         ` Greg KH
2014-02-13  2:19 Stephen Rothwell
2014-02-13  2:22 ` Stephen Rothwell
2014-02-13 17:31 ` Paul Gortmaker
2014-02-13 18:22   ` Paul Gortmaker
2014-02-13 18:28     ` Greg KH
2013-07-23  1:32 Stephen Rothwell
2013-07-23  7:24 ` Hauke Mehrtens
2013-04-02  2:34 Stephen Rothwell
2013-04-02  3:07 ` Larry Finger
2013-04-02  3:31   ` Stephen Rothwell
2013-04-02  4:07     ` Larry Finger
2012-04-12  2:24 Stephen Rothwell
2011-11-22  3:35 Stephen Rothwell
2011-11-22  8:03 ` Stanislaw Gruszka

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='CAB=NE6V12m2_u6YGxhmqjNGs9OjdOKFpCAYu5cs_Hezwwk9LLA@mail.gmail.com' \
    --to=mcgrof@qca.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=sfr@canb.auug.org.au \
    --cc=zefir.kurtisi@neratec.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).