From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
Alan Brady <alan.brady@intel.com>
Subject: Re: linux-next: Tree for Sep 20 (drivers/net/ethernet/intel/idpf/idpf_txrx.o)
Date: Tue, 19 Sep 2023 22:32:54 -0700 [thread overview]
Message-ID: <4c84eb7b-3dec-467b-934b-8a0240f7fb12@infradead.org> (raw)
In-Reply-To: <20230920133714.351f83f9@canb.auug.org.au>
On 9/19/23 20:37, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20230919:
>
> The mm tree lost its boot warning.
>
> The drm-misc tree gained a conflict against Linus' tree.
>
> Non-merge commits (relative to Linus' tree): 6006
> 3996 files changed, 459968 insertions(+), 111742 deletions(-)
>
> ----------------------------------------------------------------------------
on arm64:
when CONFIG_NET is not set:
aarch64-linux-ld: drivers/net/ethernet/intel/idpf/idpf_txrx.o: in function `idpf_rx_rsc.isra.0':
drivers/net/ethernet/intel/idpf/idpf_txrx.c:2909:(.text+0x40cc): undefined reference to `tcp_gro_complete'
--
~Randy
next prev parent reply other threads:[~2023-09-20 5:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 3:37 linux-next: Tree for Sep 20 Stephen Rothwell
2023-09-20 5:32 ` Randy Dunlap [this message]
2023-09-20 15:52 ` linux-next: Tree for Sep 20 (ppc32: ADB_CUDA Kconfig warning) Randy Dunlap
2023-09-22 0:10 ` Michael Ellerman
2023-09-22 4:51 ` Randy Dunlap
2023-10-07 17:32 ` Randy Dunlap
2023-09-20 15:55 ` linux-next: Tree for Sep 20 (objtool: intel_idle) Randy Dunlap
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=4c84eb7b-3dec-467b-934b-8a0240f7fb12@infradead.org \
--to=rdunlap@infradead.org \
--cc=alan.brady@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.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 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).