Hello,
On 17/07/2020 09:49:05-0700, Randy Dunlap wrote:
> on x86_64:
> # CONFIG_WATCHDOG is not set
>
> ld: drivers/rtc/rtc-ds1374.o: in function `ds1374_probe':
> rtc-ds1374.c:(.text+0x736): undefined reference to `watchdog_init_timeout'
> ld: rtc-ds1374.c:(.text+0x77e): undefined reference to
Hi Johnson,
On Mon, 20 Jul 2020 03:46:15 + Johnson CH Chen (陳昭勳)
wrote:
>
> > On Fri, 17 Jul 2020 09:49:05 -0700 Randy Dunlap
> > wrote:
> > > on x86_64:
> > > # CONFIG_WATCHDOG is not set
> > >
>
> Thanks for your information.
>
> It seems RTC_DRV_DS1374_WDT should be depended on RTC
gt; Subject: Re: linux-next: Tree for Jul 17 (drivers/rtc/rtc-ds1374.o)
>
> Hi Randy,
>
> [Please trim your emails a bit more, thanks]
>
> On Fri, 17 Jul 2020 09:49:05 -0700 Randy Dunlap
> wrote:
> > on x86_64:
> > # CONFIG_WATCHDOG is not set
> >
Thanks for
Hi Randy,
[Please trim your emails a bit more, thanks]
On Fri, 17 Jul 2020 09:49:05 -0700 Randy Dunlap wrote:
> on x86_64:
> # CONFIG_WATCHDOG is not set
>
> ld: drivers/rtc/rtc-ds1374.o: in function `ds1374_probe':
> rtc-ds1374.c:(.text+0x736): undefined reference to `watchdog_init_timeout'
>
On 7/17/20 4:40 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200716:
>
> New tree: init
> Changed tree: dmi (from quilt to git)
>
> My fixes tree contains:
>
> dbf24e30ce2e ("device_cgroup: Fix RCU list debugging warning")
>
> I revreted 3 commits from the powerpc tree due to re
Hi all,
Changes since 20200716:
New tree: init
Changed tree: dmi (from quilt to git)
My fixes tree contains:
dbf24e30ce2e ("device_cgroup: Fix RCU list debugging warning")
I revreted 3 commits from the powerpc tree due to reported run time
problems.
The sound tree gained a semantic conflict
On Wed, Jul 17, 2019 at 5:33 PM Darrick J. Wong wrote:
>
> On Wed, Jul 17, 2019 at 05:30:47PM +0200, Sedat Dilek wrote:
> > Hi Steven, Hi Darrick,
> >
> > Unfortunately, my build-script is not working anymore.
> >
> > I am using builddeb/mkdebian scripts.
>
> Yeah, I accidentally uploaded an inter
On Wed, Jul 17, 2019 at 05:30:47PM +0200, Sedat Dilek wrote:
> Hi Steven, Hi Darrick,
>
> Unfortunately, my build-script is not working anymore.
>
> I am using builddeb/mkdebian scripts.
Yeah, I accidentally uploaded an internal build patch yesterday which
got sucked into for-next. It's been fi
Hi Steven, Hi Darrick,
Unfortunately, my build-script is not working anymore.
I am using builddeb/mkdebian scripts.
[ BUILD-LOG ]
...
set -e; mkdir -p include/config/; { echo "5.2.0$(/bin/bash
./scripts/setlocalversion .)"; } > include/config/kernel.release.tmp;
if [ -r include/config/kernel.rel
Hi all,
Please do not add v5.4 material to your linux-next included branches
until after v5.3-rc1 has been released.
Changes since 20190716:
The kbuild tree lost its build failure.
The xfs tree gained a conflict against Linus' tree.
Non-merge commits (relative to Linus' tree): 2695
2480 files
Hi all,
Changes since 20180716:
New tree: h8300
The arm-soc tree lost its build failure.
The net-next tree gained a conflict against the net tree.
The integrity tree gained a build failure due to duplictae patches not
merging correctly. I applied a merge fix patch.
The staging tree gained a
Hi all,
Changes since 20170714:
Non-merge commits (relative to Linus' tree): 647
708 files changed, 24530 insertions(+), 8919 deletions(-)
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/k
Hi Paul,
On Sat, 18 Jul 2015 15:41:51 -0400 Paul Gortmaker
wrote:
>
> I noticed there are a bunch of new (appeared in the last day or two)
> fails spread around, so I did a triage/bisect of them so we have a
> better idea of what is going on as we start the week.
Thanks for this. Lets hope som
I noticed there are a bunch of new (appeared in the last day or two)
fails spread around, so I did a triage/bisect of them so we have a
better idea of what is going on as we start the week.
Unfortunately I was unable to reproduce the sparc fail, so I don't know
what is going on there
Biggest
Hi all,
Changes since 20150716:
Added tree: samaung-krzk
The net-next tree gained a conflict against the net tree.
The sound-asoc tree gained a build failure for which I applied a fix
patch.
The regmap tree gained conflicts against the sound-asoc tree.
I added several supplied patches to the
Hi all,
Changes since 20140716:
The mvebu tree gained conflicts against Linus' and the arm trees.
The samsung tree gained conflicts against the arm-soc tree.
The wireless-next tree lost its build failure.
The usb-gadget tree gained a conflict against Linus' tree.
The akpm tree lost its build
On Thu, Jul 18, 2013 at 12:09:16PM +1000, Stephen Rothwell wrote:
> On Thu, 18 Jul 2013 09:38:24 +1000 Stephen Rothwell
> wrote:
> > So these are the errors I got yesterday:
> > sound/soc/fsl/imx-mc13783.c:23:28: fatal error: asm/mach-types.h: No such
> > file or directory
> > #include
> > I
Hi Mark,
On Thu, 18 Jul 2013 09:38:24 +1000 Stephen Rothwell
wrote:
>
> So these are the errors I got yesterday:
>
> sound/soc/fsl/imx-mc13783.c:23:28: fatal error: asm/mach-types.h: No such
> file or directory
> #include
> ^
>
> I didn't look closely enough, bec
Hi Mark,
[Sorry for the delay, I had to go into work to find the logs of
yesterday's builds.]
On Wed, 17 Jul 2013 09:31:34 +0100 Mark Brown wrote:
>
> On Wed, Jul 17, 2013 at 02:13:35PM +1000, Stephen Rothwell wrote:
>
> > The sound-asoc tree still has its build failure so I used the version fr
On Wed, Jul 17, 2013 at 02:13:35PM +1000, Stephen Rothwell wrote:
> The sound-asoc tree still has its build failure so I used the version from
> next-20130715.
I'd have expected both of those to have been fixed. Are you sure you're
seeing the same issue?
signature.asc
Description: Digital sign
Hi all,
Changes since 20130716:
New tree: aio
The sound-asoc tree still has its build failure so I used the version from
next-20130715.
The aio tree gained a build failure for which I reverted a commit.
I have create
21 matches
Mail list logo