All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@idosch.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: linux-next: Tree for Aug 19 (drivers/net/netdevsim/dev.o)
Date: Tue, 20 Aug 2019 17:13:24 +0300	[thread overview]
Message-ID: <20190820141324.GC31968@splinter> (raw)
In-Reply-To: <92ef45a5-c933-0493-b2ff-50352fa8bf3f@infradead.org>

On Mon, Aug 19, 2019 at 09:16:13PM -0700, Randy Dunlap wrote:
> On 8/19/19 2:18 AM, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20190816:
> > 
> 
> on x86_64:
> # CONFIG_INET is not set
> 
> ld: drivers/net/netdevsim/dev.o: in function `nsim_dev_trap_report_work':
> dev.c:(.text+0x52f): undefined reference to `ip_send_check'

Thanks, Randy.

There is a fix here [1], but some changes were requested. I will send a
fix later today and Cc you.

[1] https://patchwork.ozlabs.org/patch/1149229/

  reply	other threads:[~2019-08-20 14:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19  9:18 linux-next: Tree for Aug 19 Stephen Rothwell
2019-08-19 21:53 ` linux-next: Tree for Aug 19 (gpu/drm/amd/display/) Randy Dunlap
2019-08-19 22:06 ` linux-next: Tree for Aug 19 (irqchip: irq-ingenic-tcu.c) Randy Dunlap
2019-08-19 22:11   ` Paul Cercueil
2019-08-20  1:34 ` linux-next: Tree for Aug 19 (amdgpu) Randy Dunlap
2019-08-20  1:45   ` Stephen Rothwell
2019-08-20 12:36     ` Jason Gunthorpe
2019-08-21 15:34       ` Kuehling, Felix
2019-08-21 15:34         ` Kuehling, Felix
2019-08-21 16:10         ` Jason Gunthorpe
2019-08-20  1:57 ` linux-next: Tree for Aug 19 (amdgpu #2) Randy Dunlap
2019-08-20  4:16 ` linux-next: Tree for Aug 19 (drivers/net/netdevsim/dev.o) Randy Dunlap
2019-08-20 14:13   ` Ido Schimmel [this message]
2019-08-20 18:13   ` Ido Schimmel

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=20190820141324.GC31968@splinter \
    --to=idosch@idosch.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --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 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.