From: Randy Dunlap <firstname.lastname@example.org> To: Stephen Rothwell <email@example.com>, Linux Next Mailing List <firstname.lastname@example.org> Cc: Linux Kernel Mailing List <email@example.com>, dri-devel <firstname.lastname@example.org>, intel-gfx <email@example.com> Subject: Re: linux-next: Tree for Feb 11 (drivers/gpu/drm/i915/display/intel_panel.o) Date: Thu, 11 Feb 2021 10:18:05 -0800 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> [-- Attachment #1: Type: text/plain, Size: 3098 bytes --] On 2/11/21 3:26 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20210210: > > The powerpc tree still had its build failure in the allyesconfig for > which I applied a supplied patch. > > The v4l-dvb tree lost its build failure. > > The drm-misc tree lost its build failure. > > The modules tree lost its build failure. > > The device-mapper tree gained a build failure so I used the version > from next-20210210. > > The tip tree lost its boot failure. > > The rcu tree gained conflicts against the block tree. > > The driver-core tree lost its build failure. > > The akpm-current tree gained conflicts against the fscache tree. > > Non-merge commits (relative to Linus' tree): 9533 > 9470 files changed, 385794 insertions(+), 266880 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 333 trees (counting Linus' and 87 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_ACPI is not set ld: drivers/gpu/drm/i915/display/intel_panel.o: in function `intel_backlight_device_register': intel_panel.c:(.text+0x40fb): undefined reference to `backlight_device_register' ld: drivers/gpu/drm/i915/display/intel_panel.o: in function `intel_backlight_device_unregister': intel_panel.c:(.text+0x41a4): undefined reference to `backlight_device_unregister' Full randconfig file is attached. -- ~Randy Reported-by: Randy Dunlap <firstname.lastname@example.org> [-- Attachment #2: config-r7779.gz --] [-- Type: application/gzip, Size: 29897 bytes --]
next prev parent reply other threads:[~2021-02-11 18:38 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-11 11:26 linux-next: Tree for Feb 11 Stephen Rothwell 2021-02-11 18:18 ` Randy Dunlap [this message] 2021-02-11 20:30 ` Heiko Carstens 2021-02-12 9:36 ` Vlad Buslov 2021-02-12 11:03 ` Heiko Carstens
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: linux-next: Tree for Feb 11 (drivers/gpu/drm/i915/display/intel_panel.o)' \ /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
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).