All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Copeland <me@bobcopeland.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: "Kalle Valo <kvalo@adurom.com> Kalle Valo" <kvalo@adurom.com>,
	kbuild-all@01.org, ath10k@lists.infradead.org
Subject: Re: [ath6kl:master 1344/1352] net/ipv4/ip_gre.c:138:15: error: redefinition of 'gre_flags_to_tnl_flags'
Date: Mon, 9 May 2016 18:10:34 -0400	[thread overview]
Message-ID: <20160509221034.GB2468@localhost> (raw)
In-Reply-To: <201605100555.J4I0pjyS%fengguang.wu@intel.com>

On Tue, May 10, 2016 at 05:51:06AM +0800, kbuild test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git master
> head:   140eb352c0398fd9c361e0fded58055c893db482
> commit: 13e441e25c7c41683748ffc48a30a83fa2e4ea7b [1344/1352] Merge remote-tracking branch 'wireless-drivers-next/master'
> config: x86_64-rhel (attached as .config)
> compiler: gcc-4.9 (Debian 4.9.3-14) 4.9.3
> reproduce:
>         git checkout 13e441e25c7c41683748ffc48a30a83fa2e4ea7b
>         # save the attached .config to linux build tree
>         make ARCH=x86_64 
> 
> Note: the ath6kl/master HEAD 140eb352c0398fd9c361e0fded58055c893db482 builds fine.
>       It only hurts bisectibility.
> 
> All errors (new ones prefixed by >>):

This is just a bit of merge damage from a patch that went into
both -rc7 and net-next.  I kept more than I should have from the
rc7 version, causing the build warnings.

-- 
Bob Copeland %% http://bobcopeland.com/

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

      reply	other threads:[~2016-05-09 22:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09 21:51 [ath6kl:master 1344/1352] net/ipv4/ip_gre.c:138:15: error: redefinition of 'gre_flags_to_tnl_flags' kbuild test robot
2016-05-09 22:10 ` Bob Copeland [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=20160509221034.GB2468@localhost \
    --to=me@bobcopeland.com \
    --cc=ath10k@lists.infradead.org \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=kvalo@adurom.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 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.