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>,
linux-media <linux-media@vger•kernel.org>,
Hans Verkuil <hverkuil-cisco@xs4all•nl>
Subject: Re: linux-next: Tree for Mar 11 (media/cec/core/cec-notifier.o)
Date: Thu, 11 Mar 2021 09:37:11 -0800 [thread overview]
Message-ID: <b79f8dec-df6a-70d2-f8e8-807308a59a98@infradead.org> (raw)
In-Reply-To: <20210311161449.7f58e7a3@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
On 3/10/21 9:14 PM, Stephen Rothwell wrote:
> Hi all,
>
> Warning: Some of the branches in linux-next are still based on v5.12-rc1,
> so please be careful if you are trying to bisect a bug.
>
> News: if your -next included tree is based on Linus' tree tag
> v5.12-rc1{,-dontuse} (or somewhere between v5.11 and that tag), please
> consider rebasing it onto v5.12-rc2. Also, please check any branches
> merged into your branch.
>
> Changes since 20210310:
>
on i386:
ld: drivers/media/cec/core/cec-notifier.o: in function `cec_notifier_parse_hdmi_phandle':
cec-notifier.c:(.text+0xb3): undefined reference to `of_find_i2c_device_by_node'
Full randconfig file is attached.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead•org>
[-- Attachment #2: config-r8171.gz --]
[-- Type: application/gzip, Size: 39369 bytes --]
next prev parent reply other threads:[~2021-03-11 17:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 5:14 linux-next: Tree for Mar 11 Stephen Rothwell
2021-03-11 17:37 ` Randy Dunlap [this message]
2021-03-11 18:58 ` linux-next: Tree for Mar 11 (media/cec/core/cec-notifier.o) Hans Verkuil
2021-03-11 18:18 ` linux-next: Tree for Mar 11 [drivers/vdpa/virtio_pci/vp_vdpa.ko] Randy Dunlap
2021-03-12 9:38 ` Jason Wang
2021-03-11 18:51 ` linux-next: Tree for Mar 11 (vmemmap) Randy Dunlap
2021-03-11 21:46 ` Oscar Salvador
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=b79f8dec-df6a-70d2-f8e8-807308a59a98@infradead.org \
--to=rdunlap@infradead$(echo .)org \
--cc=hverkuil-cisco@xs4all$(echo .)nl \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-media@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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