All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keller, Jacob E <jacob.e.keller@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next-queue v2 01/17] fm10k: conditionally compile DCB and DebugFS support
Date: Wed, 14 Oct 2015 18:03:46 +0000	[thread overview]
Message-ID: <1444845826.26286.31.camel@intel.com> (raw)
In-Reply-To: <20151014164235.GA26991@aiaiai.jf.intel.com>

On Wed, 2015-10-14 at 09:42 -0700, ND Linux CI Server wrote:
> Bisectability test results for configuration "intel_defconfig,x86"
> 
> Failed to build patch #3: 9800d00 fm10k: reinitialize queuing scheme after calling init_hw
> Configuration: "intel_defconfig, architecture x86".
> 
> 
> drivers/net/ethernet/intel/fm10k/fm10k_pci.c: In function ?fm10k_reinit?:
> drivers/net/ethernet/intel/fm10k/fm10k_pci.c:176:3: error: label ?reinit_err? used but not defined
>    goto reinit_err;
>    ^
> make[6]: *** [drivers/net/ethernet/intel/fm10k/fm10k_pci.o] Error 1
> Failed to build patch #4: ef14b12 fm10k: reset max_queues on init_hw_vf failure
> Configuration: "intel_defconfig, architecture x86".
> 
> 
> drivers/net/ethernet/intel/fm10k/fm10k_pci.c: In function ?fm10k_reinit?:
> drivers/net/ethernet/intel/fm10k/fm10k_pci.c:176:3: error: label ?reinit_err? used but not defined
>    goto reinit_err;
>    ^
> make[6]: *** [drivers/net/ethernet/intel/fm10k/fm10k_pci.o] Error 1

This can be fixed by just re-ordering patch 3 as patch 5, but I can
resend if you don't want to do that by hand. There is no merge conflict
when I did it via interactive rebase.

Regards,
Jake

       reply	other threads:[~2015-10-14 18:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151014164235.GA26991@aiaiai.jf.intel.com>
2015-10-14 18:03 ` Keller, Jacob E [this message]
2015-10-14 19:48   ` [Intel-wired-lan] [next-queue v2 01/17] fm10k: conditionally compile DCB and DebugFS support Jeff Kirsher
2015-10-14 20:12     ` Keller, Jacob E
2015-10-14 16:32 Jacob Keller
2015-10-15  1:00 ` Allan, Bruce W

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=1444845826.26286.31.camel@intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=intel-wired-lan@osuosl.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.