Hi all,
This is actually just a warning.
On Fri, 16 Apr 2021 13:48:27 +1000 Stephen Rothwell
wrote:
>
> Hi all,
>
> After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> In file included from drivers/memstick/host/r592.h:13,
>
Hi all,
After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
In file included from drivers/memstick/host/r592.h:13,
from drivers/memstick/host/r592.c:21:
drivers/memstick/host/r592.c: In function 'r592_flush_fifo_write':
Hi all,
After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/mmc/host/sdhci-acpi.c: In function 'amd_select_drive_strength':
drivers/mmc/host/sdhci-acpi.c:562:39: error: 'SDHCI_PRESET_DRV_SHIFT'
undeclared (first use in this function); did you
Hi all,
After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/mmc/host/davinci_mmc.c: In function 'mmc_davinci_set_ios':
drivers/mmc/host/davinci_mmc.c:696:19: error: 'mmc' redeclared as different
kind of symbol
696 | struct mmc_host *mmc =
Stephen Rothwell writes:
> Hi all,
>
> After merging the mmc tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c: In function
> 'brcmf_sdiod_probe':
>
+ Linus
On Tue, 2 Jun 2020 at 05:44, Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the mmc tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c: In function
> 'brcmf_sdiod_probe':
>
Hi all,
After merging the mmc tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c: In function
'brcmf_sdiod_probe':
drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c:915:7: error:
Hi Stephen,
On Mon, May 18, 2020 at 6:27 AM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> WARNING: modpost: missing MODULE_LICENSE() in
> drivers/mmc/host/meson-mx-sdhc-clkc.o
> see
Hi all,
After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
WARNING: modpost: missing MODULE_LICENSE() in
drivers/mmc/host/meson-mx-sdhc-clkc.o
see include/linux/module.h for more information
ERROR: modpost: "meson_mx_sdhc_register_clkc"
Hi,
On Thursday 15 February 2018 06:19 AM, Stephen Rothwell wrote:
> Hi Ulf,
>
> After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/mmc/host/sdhci-omap.c: In function 'sdhci_omap_set_timing':
> drivers/mmc/host/sdhci-omap.c:466:8: error:
Hi,
On Thursday 15 February 2018 06:19 AM, Stephen Rothwell wrote:
> Hi Ulf,
>
> After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/mmc/host/sdhci-omap.c: In function 'sdhci_omap_set_timing':
> drivers/mmc/host/sdhci-omap.c:466:8: error:
Hi Ulf,
After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/mmc/host/sdhci-omap.c: In function 'sdhci_omap_set_timing':
drivers/mmc/host/sdhci-omap.c:466:8: error: implicit declaration of function
'pinctrl_select_state'; did you mean
Hi Ulf,
After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/mmc/host/sdhci-omap.c: In function 'sdhci_omap_set_timing':
drivers/mmc/host/sdhci-omap.c:466:8: error: implicit declaration of function
'pinctrl_select_state'; did you mean
Hi Stephen,
On Wed, Jun 04 2014, Chris Ball wrote:
> On Tue, Jun 03 2014, Stephen Rothwell wrote:
>>> This is back again. I have no idea why I didn't get this failure on
>>> Friday. Please, guys, go through your tree and fix this problem once
>>> and for all. Grep is your friend.
>>>
>>> I
Hi Stephen,
On Tue, Jun 03 2014, Stephen Rothwell wrote:
>> This is back again. I have no idea why I didn't get this failure on
>> Friday. Please, guys, go through your tree and fix this problem once
>> and for all. Grep is your friend.
>>
>> I have used the mmc tree from next-20140522 again
Hi Stephen,
On Tue, Jun 03 2014, Stephen Rothwell wrote:
This is back again. I have no idea why I didn't get this failure on
Friday. Please, guys, go through your tree and fix this problem once
and for all. Grep is your friend.
I have used the mmc tree from next-20140522 again for today.
Hi Stephen,
On Wed, Jun 04 2014, Chris Ball wrote:
On Tue, Jun 03 2014, Stephen Rothwell wrote:
This is back again. I have no idea why I didn't get this failure on
Friday. Please, guys, go through your tree and fix this problem once
and for all. Grep is your friend.
I have used the mmc
Hi Chris,
On Mon, 2 Jun 2014 15:11:41 +1000 Stephen Rothwell
wrote:
>
> On Mon, 26 May 2014 14:07:35 +1000 Stephen Rothwell
> wrote:
> >
> > After merging the mmc tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> >
> > drivers/mmc/host/sdhci-s3c.c: In function
Hi Chris,
On Mon, 2 Jun 2014 15:11:41 +1000 Stephen Rothwell s...@canb.auug.org.au
wrote:
On Mon, 26 May 2014 14:07:35 +1000 Stephen Rothwell s...@canb.auug.org.au
wrote:
After merging the mmc tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
Hi,
On Mon, Jun 02 2014, Mike Turquette wrote:
>> Hi Mike, Chris,
>>
>> So, the proper thing would be to let Mike to carry the above patch
>> though his clk tree instead.
>>
>> Could we arrange that?
>
> I'm happy to take it with Chris' Acked-by.
Thanks, please do:
Acked-by: Chris Ball
(Ulf
On 30 May 2014 05:23, Stephen Rothwell wrote:
> Hi Chris,
>
> After merging the mmc tree, today's linux-next build (arm multi_v7_defconfig)
> failed like this:
>
> drivers/mmc/host/sunxi-mmc.c:25:29: fatal error: linux/clk/sunxi.h: No such
> file or directory
>
> Caused by commit 19b7f796c375
On 30 May 2014 05:23, Stephen Rothwell s...@canb.auug.org.au wrote:
Hi Chris,
After merging the mmc tree, today's linux-next build (arm multi_v7_defconfig)
failed like this:
drivers/mmc/host/sunxi-mmc.c:25:29: fatal error: linux/clk/sunxi.h: No such
file or directory
Caused by commit
Hi,
On Mon, Jun 02 2014, Mike Turquette wrote:
Hi Mike, Chris,
So, the proper thing would be to let Mike to carry the above patch
though his clk tree instead.
Could we arrange that?
I'm happy to take it with Chris' Acked-by.
Thanks, please do:
Acked-by: Chris Ball ch...@printf.net
Hi Chris,
On Mon, 26 May 2014 14:07:35 +1000 Stephen Rothwell
wrote:
>
> After merging the mmc tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/mmc/host/sdhci-s3c.c: In function 'sdhci_s3c_notify_change':
> drivers/mmc/host/sdhci-s3c.c:402:25: error:
Hi Chris,
On Mon, 26 May 2014 14:07:35 +1000 Stephen Rothwell s...@canb.auug.org.au
wrote:
After merging the mmc tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/mmc/host/sdhci-s3c.c: In function 'sdhci_s3c_notify_change':
Hi Chris,
After merging the mmc tree, today's linux-next build (arm multi_v7_defconfig)
failed like this:
drivers/mmc/host/sunxi-mmc.c:25:29: fatal error: linux/clk/sunxi.h: No such
file or directory
Caused by commit 19b7f796c375 ("mmc: sunxi: Add driver for SD/MMC hosts
found on Allwinner
Hi Chris,
After merging the mmc tree, today's linux-next build (arm multi_v7_defconfig)
failed like this:
drivers/mmc/host/sunxi-mmc.c:25:29: fatal error: linux/clk/sunxi.h: No such
file or directory
Caused by commit 19b7f796c375 (mmc: sunxi: Add driver for SD/MMC hosts
found on Allwinner
Hi Chris,
After merging the mmc tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/mmc/host/sdhci-s3c.c: In function 'sdhci_s3c_notify_change':
drivers/mmc/host/sdhci-s3c.c:402:25: error: 'struct sdhci_host' has no member
named 'card_tasklet'
Caused by commit
Hi Chris,
After merging the mmc tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/mmc/host/sdhci-s3c.c: In function 'sdhci_s3c_notify_change':
drivers/mmc/host/sdhci-s3c.c:402:25: error: 'struct sdhci_host' has no member
named 'card_tasklet'
Caused by commit
On 05/23/2014 07:32 AM, Stephen Rothwell wrote:
After merging the mmc tree, today's linux-next build (arm multi_v7_defconfig)
failed like this:
drivers/mmc/host/sdhci-dove.c: In function 'sdhci_dove_carddetect_irq':
drivers/mmc/host/sdhci-dove.c:42:24: error: 'struct sdhci_host' has no member
On 05/23/2014 07:32 AM, Stephen Rothwell wrote:
After merging the mmc tree, today's linux-next build (arm multi_v7_defconfig)
failed like this:
drivers/mmc/host/sdhci-dove.c: In function 'sdhci_dove_carddetect_irq':
drivers/mmc/host/sdhci-dove.c:42:24: error: 'struct sdhci_host' has no member
Hi Chris,
After merging the mmc tree, today's linux-next build (arm multi_v7_defconfig)
failed like this:
drivers/mmc/host/sdhci-dove.c: In function 'sdhci_dove_carddetect_irq':
drivers/mmc/host/sdhci-dove.c:42:24: error: 'struct sdhci_host' has no member
named 'card_tasklet'
Caused by commit
Hi Chris,
After merging the mmc tree, today's linux-next build (arm multi_v7_defconfig)
failed like this:
drivers/mmc/host/sdhci-dove.c: In function 'sdhci_dove_carddetect_irq':
drivers/mmc/host/sdhci-dove.c:42:24: error: 'struct sdhci_host' has no member
named 'card_tasklet'
Caused by commit
Hi,
On Tue, Apr 22 2014, Ulf Hansson wrote:
> Until we work out the dependency issue caused by the above commit,
> could you please drop the following patches from your mmc-next
> branch!?
>
> df1a292 mmc: add support for HS400 mode of eMMC5.0
> f27a5d7 mmc: rework selection of bus speed mode
>
On 22 April 2014 05:06, Stephen Rothwell wrote:
> Hi Chris,
>
> After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/net/wireless/rsi/rsi_91x_sdio.c: In function 'rsi_reset_card':
> drivers/net/wireless/rsi/rsi_91x_sdio.c:288:20: error:
On 22 April 2014 05:06, Stephen Rothwell s...@canb.auug.org.au wrote:
Hi Chris,
After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/net/wireless/rsi/rsi_91x_sdio.c: In function 'rsi_reset_card':
drivers/net/wireless/rsi/rsi_91x_sdio.c:288:20:
Hi,
On Tue, Apr 22 2014, Ulf Hansson wrote:
Until we work out the dependency issue caused by the above commit,
could you please drop the following patches from your mmc-next
branch!?
df1a292 mmc: add support for HS400 mode of eMMC5.0
f27a5d7 mmc: rework selection of bus speed mode
e64f275
On Tue, April 22, 2014, Stephen Rothwell wrote:
> Hi Chris,
>
> After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/net/wireless/rsi/rsi_91x_sdio.c: In function 'rsi_reset_card':
> drivers/net/wireless/rsi/rsi_91x_sdio.c:288:20: error:
Hi Chris,
After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/net/wireless/rsi/rsi_91x_sdio.c: In function 'rsi_reset_card':
drivers/net/wireless/rsi/rsi_91x_sdio.c:288:20: error: 'MMC_STATE_HIGHSPEED'
undeclared (first use in this function)
Hi Chris,
After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/net/wireless/rsi/rsi_91x_sdio.c: In function 'rsi_reset_card':
drivers/net/wireless/rsi/rsi_91x_sdio.c:288:20: error: 'MMC_STATE_HIGHSPEED'
undeclared (first use in this function)
On Tue, April 22, 2014, Stephen Rothwell wrote:
Hi Chris,
After merging the mmc tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/net/wireless/rsi/rsi_91x_sdio.c: In function 'rsi_reset_card':
drivers/net/wireless/rsi/rsi_91x_sdio.c:288:20: error:
Hi,
On Tue, Dec 17 2013, Shawn Guo wrote:
> Please drop fc4fafac9656 ("ARM: dts: sabresd: add usdhc4 support") from
> your tree. It should go via my tree (with a rebase). Sorry, I did not
> notice it early.
Sorry for missing this thread, everyone -- I've dropped this patch
from mmc-next now.
Hi,
On Tue, Dec 17 2013, Shawn Guo wrote:
Please drop fc4fafac9656 (ARM: dts: sabresd: add usdhc4 support) from
your tree. It should go via my tree (with a rebase). Sorry, I did not
notice it early.
Sorry for missing this thread, everyone -- I've dropped this patch
from mmc-next now.
-
Hi Shawn,
On Mon, 6 Jan 2014 14:44:08 +0800 Shawn Guo wrote:
>
> Okay, I missed your point. The resolution needs the additional changes
> as below.
Thanks, I applied the following as a merge fix patch today and will carry
it as necessary.
From: Stephen Rothwell
Date: Tue, 7 Jan 2014 14:20:53
Hi Shawn,
On Mon, 6 Jan 2014 14:44:08 +0800 Shawn Guo shawn@linaro.org wrote:
Okay, I missed your point. The resolution needs the additional changes
as below.
Thanks, I applied the following as a merge fix patch today and will carry
it as necessary.
From: Stephen Rothwell
Hi Shawn,
On Mon, 6 Jan 2014 14:44:08 +0800 Shawn Guo wrote:
>
> Okay, I missed your point. The resolution needs the additional changes
> as below.
>
> Shawn
>
> diff --git a/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
> b/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
> index 91e5dd4..8b05648 100644
>
On Mon, Jan 6, 2014 at 2:46 PM, Shawn Guo wrote:
> On Mon, Jan 06, 2014 at 02:30:00PM +0800, Dong Aisheng wrote:
>> Hi Shawn,
>>
>> How do you suggest to fix this issue?
>> Can we cook a patch for it directly based on linux-next tree?
>
> No, we can not. No patch should be targeting linux-next
On Mon, Jan 06, 2014 at 02:30:00PM +0800, Dong Aisheng wrote:
> Hi Shawn,
>
> How do you suggest to fix this issue?
> Can we cook a patch for it directly based on linux-next tree?
No, we can not. No patch should be targeting linux-next tree. I just
gave a resolution to Stephen. Before Chris
On Mon, Jan 06, 2014 at 05:22:43PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 17 Dec 2013 16:06:19 +0800 Dong Aisheng wrote:
> >
> > I tested that Chris tree does not have problem.
> > It's caused by IMX tree updates.
> >
> > Chris,
> > Is the way Shawn suggested OK for you?
>
> Can
Hi Stephen,
On Mon, Jan 06, 2014 at 05:22:43PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 17 Dec 2013 16:06:19 +0800 Dong Aisheng wrote:
> >
> > I tested that Chris tree does not have problem.
> > It's caused by IMX tree updates.
> >
> > Chris,
> > Is the way Shawn suggested OK for
Hi Shawn,
How do you suggest to fix this issue?
Can we cook a patch for it directly based on linux-next tree?
Regards
Dong Aisheng
On Mon, Jan 6, 2014 at 2:22 PM, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 17 Dec 2013 16:06:19 +0800 Dong Aisheng wrote:
>>
>> I tested that Chris tree does
Hi all,
On Tue, 17 Dec 2013 16:06:19 +0800 Dong Aisheng wrote:
>
> I tested that Chris tree does not have problem.
> It's caused by IMX tree updates.
>
> Chris,
> Is the way Shawn suggested OK for you?
Can we have some resolution of this please? This failed to build again
today so I have used
Hi all,
On Tue, 17 Dec 2013 16:06:19 +0800 Dong Aisheng donga...@gmail.com wrote:
I tested that Chris tree does not have problem.
It's caused by IMX tree updates.
Chris,
Is the way Shawn suggested OK for you?
Can we have some resolution of this please? This failed to build again
today so
Hi Shawn,
How do you suggest to fix this issue?
Can we cook a patch for it directly based on linux-next tree?
Regards
Dong Aisheng
On Mon, Jan 6, 2014 at 2:22 PM, Stephen Rothwell s...@canb.auug.org.au wrote:
Hi all,
On Tue, 17 Dec 2013 16:06:19 +0800 Dong Aisheng donga...@gmail.com wrote:
Hi Stephen,
On Mon, Jan 06, 2014 at 05:22:43PM +1100, Stephen Rothwell wrote:
Hi all,
On Tue, 17 Dec 2013 16:06:19 +0800 Dong Aisheng donga...@gmail.com wrote:
I tested that Chris tree does not have problem.
It's caused by IMX tree updates.
Chris,
Is the way Shawn suggested OK
On Mon, Jan 06, 2014 at 05:22:43PM +1100, Stephen Rothwell wrote:
Hi all,
On Tue, 17 Dec 2013 16:06:19 +0800 Dong Aisheng donga...@gmail.com wrote:
I tested that Chris tree does not have problem.
It's caused by IMX tree updates.
Chris,
Is the way Shawn suggested OK for you?
Can
On Mon, Jan 06, 2014 at 02:30:00PM +0800, Dong Aisheng wrote:
Hi Shawn,
How do you suggest to fix this issue?
Can we cook a patch for it directly based on linux-next tree?
No, we can not. No patch should be targeting linux-next tree. I just
gave a resolution to Stephen. Before Chris shows
On Mon, Jan 6, 2014 at 2:46 PM, Shawn Guo shawn@linaro.org wrote:
On Mon, Jan 06, 2014 at 02:30:00PM +0800, Dong Aisheng wrote:
Hi Shawn,
How do you suggest to fix this issue?
Can we cook a patch for it directly based on linux-next tree?
No, we can not. No patch should be targeting
Hi Shawn,
On Mon, 6 Jan 2014 14:44:08 +0800 Shawn Guo shawn@linaro.org wrote:
Okay, I missed your point. The resolution needs the additional changes
as below.
Shawn
diff --git a/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
b/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
index 91e5dd4..8b05648
On Tue, 17 Dec 2013 13:28:38 +1100 Stephen Rothwell
wrote:
>
> Hi Chris,
>
> ping?
ping again - I am still getting this error.
> On Fri, 13 Dec 2013 12:57:16 +1100 Stephen Rothwell
> wrote:
> >
> > After merging the mmc tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like
On Tue, 17 Dec 2013 13:28:38 +1100 Stephen Rothwell s...@canb.auug.org.au
wrote:
Hi Chris,
ping?
ping again - I am still getting this error.
On Fri, 13 Dec 2013 12:57:16 +1100 Stephen Rothwell s...@canb.auug.org.au
wrote:
After merging the mmc tree, today's linux-next build (arm
I tested that Chris tree does not have problem.
It's caused by IMX tree updates.
Chris,
Is the way Shawn suggested OK for you?
Regards
Dong Aisheng
On Tue, Dec 17, 2013 at 11:16 AM, Shawn Guo wrote:
> Hi Chris,
>
> Please drop fc4fafac9656 ("ARM: dts: sabresd: add usdhc4 support") from
> your
I tested that Chris tree does not have problem.
It's caused by IMX tree updates.
Chris,
Is the way Shawn suggested OK for you?
Regards
Dong Aisheng
On Tue, Dec 17, 2013 at 11:16 AM, Shawn Guo shawn@linaro.org wrote:
Hi Chris,
Please drop fc4fafac9656 (ARM: dts: sabresd: add usdhc4
Hi Chris,
Please drop fc4fafac9656 ("ARM: dts: sabresd: add usdhc4 support") from
your tree. It should go via my tree (with a rebase). Sorry, I did not
notice it early.
Shawn
On Tue, Dec 17, 2013 at 11:07:19AM +0800, Dong Aisheng wrote:
> Hi Stephen,
>
> Sorry, i just see this mail.
> It
Hi Stephen,
Sorry, i just see this mail.
It seems the imx pinctrl dt binding has changes since Chris pick my patch.
I will fix it ASAP.
Regards
Dong Aisheng
On Tue, Dec 17, 2013 at 10:28 AM, Stephen Rothwell
wrote:
> Hi Chris,
>
> ping?
>
> On Fri, 13 Dec 2013 12:57:16 +1100 Stephen Rothwell
Hi Chris,
ping?
On Fri, 13 Dec 2013 12:57:16 +1100 Stephen Rothwell
wrote:
>
> After merging the mmc tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> ERROR (phandle_references): Reference to non-existent node or label
> "pinctrl_usdhc4_1"
>
> ERROR: Input tree
Hi Chris,
ping?
On Fri, 13 Dec 2013 12:57:16 +1100 Stephen Rothwell s...@canb.auug.org.au
wrote:
After merging the mmc tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
ERROR (phandle_references): Reference to non-existent node or label
pinctrl_usdhc4_1
ERROR:
Hi Stephen,
Sorry, i just see this mail.
It seems the imx pinctrl dt binding has changes since Chris pick my patch.
I will fix it ASAP.
Regards
Dong Aisheng
On Tue, Dec 17, 2013 at 10:28 AM, Stephen Rothwell s...@canb.auug.org.au
wrote:
Hi Chris,
ping?
On Fri, 13 Dec 2013 12:57:16 +1100
Hi Chris,
Please drop fc4fafac9656 (ARM: dts: sabresd: add usdhc4 support) from
your tree. It should go via my tree (with a rebase). Sorry, I did not
notice it early.
Shawn
On Tue, Dec 17, 2013 at 11:07:19AM +0800, Dong Aisheng wrote:
Hi Stephen,
Sorry, i just see this mail.
It seems the
Hi Chris,
After merging the mmc tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
ERROR (phandle_references): Reference to non-existent node or label
"pinctrl_usdhc4_1"
ERROR: Input tree has errors, aborting (use -f to force output)
make[2]: ***
Hi Chris,
After merging the mmc tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
ERROR (phandle_references): Reference to non-existent node or label
pinctrl_usdhc4_1
ERROR: Input tree has errors, aborting (use -f to force output)
make[2]: ***
71 matches
Mail list logo
