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>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Lin Lei <linlei@linux.alibaba.com>,
Guo Ren <guoren@linux.alibaba.com>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: linux-next: Tree for Nov 5 [drivers/net/ethernet/stmicro/stmmac/dwmac-thead.ko]
Date: Thu, 5 Nov 2020 12:29:48 -0800 [thread overview]
Message-ID: <1890051c-f317-af83-7cba-ff858c6d1f5c@infradead.org> (raw)
In-Reply-To: <20201105170604.6588a06e@canb.auug.org.au>
On 11/4/20 10:06 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20201104:
>
> The drm-intel-fixes tree lost its build failure.
>
> The drm-msm tree gained conflicts against the drm and drm-misc trees.
>
> The mfd tree gained a build failure so I used the version from
> next-20201104.
>
> The pinctrl tree lost its build failure.
>
> The akpm-current tree gained a build failure for which I reverted
> a commit.
>
> Non-merge commits (relative to Linus' tree): 3085
> 3498 files changed, 376683 insertions(+), 40297 deletions(-)
>
> ----------------------------------------------------------------------------
>
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you
> are tracking the linux-next tree using git, you should not use "git pull"
> to do so as that will try to merge the new linux-next release with the
> old one. You should use "git fetch" and checkout or reset to the new
> master.
>
> You can see which trees have been included by looking in the Next/Trees
> file in the source. There are also quilt-import.log and merge.log
> files in the Next directory. Between each merge, the tree was built
> with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
> multi_v7_defconfig for arm and a native build of tools/perf. After
> the final fixups (if any), I do an x86_64 modules_install followed by
> builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
> ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
> and sparc64 defconfig and htmldocs. And finally, a simple boot test
> of the powerpc pseries_le_defconfig kernel in qemu (with and without
> kvm enabled).
>
> Below is a summary of the state of the merge.
>
> I am currently merging 327 trees (counting Linus' and 85 trees of bug
> fix patches pending for the current merge release).
>
> Stats about the size of the tree over time can be seen at
> http://neuling.org/linux-next-size.html .
>
> Status of my local build tests will be at
> http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
> advice about cross compilers/configs that work, we are always open to add
> more builds.
>
> Thanks to Randy Dunlap for doing many randconfig builds. And to Paul
> Gortmaker for triage and bug fixes.
>
on x86_64:
CONFIG_STMMAC_ETH=m
# CONFIG_STMMAC_PLATFORM is not set
CONFIG_DWMAC_INTEL=m
CONFIG_STMMAC_PCI=m
dwmac-thead.c is always built but it seems to expect (require) that
stmmac_platform.c is also always built, but the latter has a Kconfig
option that can be (is) disabled, resulting in build errors:
ERROR: modpost: "stmmac_pltfr_pm_ops" [drivers/net/ethernet/stmicro/stmmac/dwmac-thead.ko] undefined!
ERROR: modpost: "stmmac_pltfr_remove" [drivers/net/ethernet/stmicro/stmmac/dwmac-thead.ko] undefined!
ERROR: modpost: "stmmac_remove_config_dt" [drivers/net/ethernet/stmicro/stmmac/dwmac-thead.ko] undefined!
ERROR: modpost: "stmmac_probe_config_dt" [drivers/net/ethernet/stmicro/stmmac/dwmac-thead.ko] undefined!
ERROR: modpost: "stmmac_get_platform_resources" [drivers/net/ethernet/stmicro/stmmac/dwmac-thead.ko] undefined!
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
next prev parent reply other threads:[~2020-11-05 20:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 6:06 linux-next: Tree for Nov 5 Stephen Rothwell
2020-11-05 16:34 ` linux-next: Tree for Nov 5 [drivers/auxdisplay/hd44780_common.ko] Randy Dunlap
2020-11-05 20:29 ` Randy Dunlap [this message]
2020-11-10 7:50 ` linux-next: Tree for Nov 5 Anders Roxell
2020-11-10 9:17 ` Dmitry Vyukov
2020-11-10 9:25 ` Anders Roxell
2020-11-10 9:36 ` Dmitry Vyukov
2020-11-10 13:54 ` Marco Elver
2020-11-10 15:42 ` Anders Roxell
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=1890051c-f317-af83-7cba-ff858c6d1f5c@infradead.org \
--to=rdunlap@infradead.org \
--cc=guoren@linux.alibaba.com \
--cc=kuba@kernel.org \
--cc=linlei@linux.alibaba.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).