Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: michael.chan@broadcom.com
Cc: kubakici@wp.pl, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] bnxt_en: Fix randconfig build errors.
Date: Sat, 28 Oct 2017 18:24:35 +0900 (KST)	[thread overview]
Message-ID: <20171028.182435.2090697905394540428.davem@davemloft.net> (raw)
In-Reply-To: <1509170170-14847-1-git-send-email-michael.chan@broadcom.com>

From: Michael Chan <michael.chan@broadcom.com>
Date: Sat, 28 Oct 2017 01:56:10 -0400

> Fix undefined symbols when CONFIG_VLAN_8021Q or CONFIG_INET is not set.
> 
> Fixes: 8c95f773b4a3 ("bnxt_en: add support for Flower based vxlan encap/decap offload")
> Reported-by: Jakub Kicinski <kubakici@wp.pl>
> Signed-off-by: Michael Chan <michael.chan@broadcom.com>

Applied, thanks Michael.

      parent reply	other threads:[~2017-10-28  9:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-28  5:56 [PATCH net-next] bnxt_en: Fix randconfig build errors Michael Chan
2017-10-28  6:05 ` Yunsheng Lin
2017-10-28  6:15   ` Jakub Kicinski
2017-10-28  6:41     ` Michael Chan
2017-10-28  9:24 ` David Miller [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=20171028.182435.2090697905394540428.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=kubakici@wp.pl \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox