On Fri, May 22, 2020 at 11:22:39AM -0700, Randy Dunlap wrote:
> On 5/18/20 9:20 AM, Jeff LaBundy wrote:
> > Hi Randy et al,
> >
> > On Mon, May 18, 2020 at 08:42:43AM -0700, Randy Dunlap wrote:
> >> On 5/18/20 3:57 AM, Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> Changes since 20200515:
> >>>
On 5/18/20 9:20 AM, Jeff LaBundy wrote:
> Hi Randy et al,
>
> On Mon, May 18, 2020 at 08:42:43AM -0700, Randy Dunlap wrote:
>> On 5/18/20 3:57 AM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20200515:
>>>
>>
>> on i386:
>>
>>
>> CONFIG_REGMAP_I2C=y
>> CONFIG_I2C=m
>>
>> WARNING: unme
Hi Randy,
On Mon, May 18, 2020 at 5:01 PM Randy Dunlap wrote:
>
> On 5/18/20 3:57 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20200515:
> >
>
> on i386:
>
> ../drivers/infiniband/ulp/rtrs/rtrs-clt.c: In function ‘alloc_sess’:
> ../drivers/infiniband/ulp/rtrs/rtrs-clt.c:1447:42:
On 5/18/20 3:57 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200515:
>
Hi,
I don't know if this is a 'tip' thing or a gcc version thing
or if it's only on i386 + certain configs, but I only see it on
i386 builds from today's linux-next or mmotm of 20200515.
../arch/x86/mm/pgtable.
Hi Randy et al,
On Mon, May 18, 2020 at 08:42:43AM -0700, Randy Dunlap wrote:
> On 5/18/20 3:57 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20200515:
> >
>
> on i386:
>
>
> CONFIG_REGMAP_I2C=y
> CONFIG_I2C=m
>
> WARNING: unmet direct dependencies detected for REGMAP_I2C
>
On 5/18/20 3:57 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200515:
>
on i386:
CONFIG_REGMAP_I2C=y
CONFIG_I2C=m
WARNING: unmet direct dependencies detected for REGMAP_I2C
Depends on [m]: I2C [=m]
Selected by [y]:
- INPUT_IQS269A [=y] && !UML && INPUT [=y] && INPUT_MISC [=y
On 5/18/20 3:57 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200515:
>
on i386:
../drivers/infiniband/ulp/rtrs/rtrs-clt.c: In function ‘alloc_sess’:
../drivers/infiniband/ulp/rtrs/rtrs-clt.c:1447:42: error:
‘BLK_MAX_SEGMENT_SIZE’ undeclared (first use in this function); did you me
Hi all,
Changes since 20200515:
My fixes tree contains:
bc0714455848 ("device_cgroup: Fix RCU list debugging warning")
7c865b3b52d1 ("drm/msm: Fix undefined "rd_full" link error")
The mtd-fixes tree gained a build failure for which I reverted a commit.
The qcom tree still had its build fai
Hi all,
Changes since 20170517:
The netfilter tree still had its build failure for which I applied a
supplied fix patch.
The file-locks tree lost its build failure.
The sound tree lost its build failure.
The scsi-mkp tree lost its build failure.
Non-merge commits (relative to Linus' tree): 14
On Wed, May 18, 2016 at 08:19:36AM -0700, Randy Dunlap wrote:
> On 05/17/16 21:30, Stephen Rothwell wrote:
> > Hi all,
> >
> > Please do not add any v4.8 destined material to your linux-next included
> > branches until after v4.7-rc1 has been released.
Apologies, I put rcu/next in the wrong place
On 05/17/16 21:30, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v4.8 destined material to your linux-next included
> branches until after v4.7-rc1 has been released.
>
> Changes since 20160517:
>
on i386:
In file included from ../kernel/rcu/tree.c:4209:0:
../kernel/rcu/tree_plug
Hi all,
Please do not add any v4.8 destined material to your linux-next included
branches until after v4.7-rc1 has been released.
Changes since 20160517:
New tree: dax-misc
The dax-misc tree gained a conflict against the nvdimm tree.
The akpm-current tree gained a conflict against the dax-misc
Hi Andrew,
On Thu, 21 May 2015 10:17:48 +1000 Stephen Rothwell
wrote:
>
> On Wed, 20 May 2015 13:03:20 -0700 Andrew Morton
> wrote:
> >
> > I dropped
> >
> > memory-failure-export-page_type-and-action-result.patch
> > memory-failure-change-type-of-action_results-param-3-to-enum.patch
> > trac
Hi Andrew,
On Wed, 20 May 2015 13:03:20 -0700 Andrew Morton
wrote:
>
> I dropped
>
> memory-failure-export-page_type-and-action-result.patch
> memory-failure-change-type-of-action_results-param-3-to-enum.patch
> tracing-add-trace-event-for-memory-failure.patch
OK, I have dropped them from linu
On Wed, 20 May 2015 13:41:57 +0800 Xie XiuQi wrote:
> On 2015/5/19 10:49, Naoya Horiguchi wrote:
> > On Mon, May 18, 2015 at 08:20:07AM -0700, Randy Dunlap wrote:
> >> On 05/18/15 01:52, Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> Changes since 20150515:
> >>>
> >>
> >> on i386:
> >>
> >> m
On 2015/5/20 14:09, Naoya Horiguchi wrote:
> On Wed, May 20, 2015 at 01:41:57PM +0800, Xie XiuQi wrote:
> ...
>>
>> Hi Naoya,
>>
>> This patch will introduce another build error with attched config file.
>>
>> drivers/built-in.o:(__tracepoints+0x500): multiple definition of
>> `__tracepoint_aer_ev
On Wed, May 20, 2015 at 01:41:57PM +0800, Xie XiuQi wrote:
...
>
> Hi Naoya,
>
> This patch will introduce another build error with attched config file.
>
> drivers/built-in.o:(__tracepoints+0x500): multiple definition of
> `__tracepoint_aer_event'
> mm/built-in.o:(__tracepoints+0x398): first d
On Tue, May 19, 2015 at 09:46:36AM -0400, Steven Rostedt wrote:
...
> > diff --git a/include/ras/ras_event.h b/include/ras/ras_event.h
> > index 1443d79e4fe6..43054c0fcf65 100644
> > --- a/include/ras/ras_event.h
> > +++ b/include/ras/ras_event.h
> > @@ -1,6 +1,8 @@
> > #undef TRACE_SYSTEM
> > #d
On 2015/5/19 10:49, Naoya Horiguchi wrote:
> On Mon, May 18, 2015 at 08:20:07AM -0700, Randy Dunlap wrote:
>> On 05/18/15 01:52, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20150515:
>>>
>>
>> on i386:
>>
>> mm/built-in.o: In function `action_result':
>> memory-failure.c:(.text+0x344a
On Tue, 19 May 2015 02:49:34 +
Naoya Horiguchi wrote:
> On Mon, May 18, 2015 at 08:20:07AM -0700, Randy Dunlap wrote:
> > On 05/18/15 01:52, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Changes since 20150515:
> > >
> >
> > on i386:
> >
> > mm/built-in.o: In function `action_result':
On 05/18/15 19:49, Naoya Horiguchi wrote:
> On Mon, May 18, 2015 at 08:20:07AM -0700, Randy Dunlap wrote:
>> On 05/18/15 01:52, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20150515:
>>>
>>
>> on i386:
>>
>> mm/built-in.o: In function `action_result':
>> memory-failure.c:(.text+0x344a5
On Mon, May 18, 2015 at 08:20:07AM -0700, Randy Dunlap wrote:
> On 05/18/15 01:52, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20150515:
> >
>
> on i386:
>
> mm/built-in.o: In function `action_result':
> memory-failure.c:(.text+0x344a5): undefined reference to
> `__tracepoint_mem
On 05/18/15 01:52, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150515:
>
on i386:
mm/built-in.o: In function `action_result':
memory-failure.c:(.text+0x344a5): undefined reference to
`__tracepoint_memory_failure_event'
memory-failure.c:(.text+0x344d5): undefined reference to
`__trac
Hi all,
Changes since 20150515:
The net-next tree gained a conflict against the net tree.
The target-updates tree lost its build failure.
Non-merge commits (relative to Linus' tree): 4438
4109 files changed, 202202 insertions(+), 100037 deletions(-)
---
24 matches
Mail list logo
