Hi,
On Mon, 14 Oct 2019 08:30:02 -0700
Randy Dunlap wrote:
> On 10/13/19 11:47 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20191011:
> >
>
> on x86_64:
>
> HOSTCC arch/x86/tools/insn_decoder_test
> HOSTCC arch/x86/tools/insn_sanity
> TESTposttest
> arch/x86/tool
On 10/13/19 11:47 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20191011:
>
on x86_64:
HOSTCC arch/x86/tools/insn_decoder_test
HOSTCC arch/x86/tools/insn_sanity
TESTposttest
arch/x86/tools/insn_decoder_test: warning: Found an x86 instruction decoder
bug, please report thi
On 10/13/19 11:47 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20191011:
>
on i386:
ld: sound/soc/sof/control.o: in function `snd_sof_switch_put':
control.c:(.text+0x49a): undefined reference to `ledtrig_audio_set'
ld: control.c:(.text+0x4d1): undefined reference to `ledtrig_audio_se
Hi all,
Changes since 20191011:
The net-next tree gained a conflict against the net tree.
The bpf-next tree gained conflicts against the net tree.
The akpm tree lost a patch taht turned up elsewhere.
Non-merge commits (relative to Linus' tree): 3676
3784 files changed, 128699 insertions(+), 6
Hi all,
Please do *not* add any v4.10 material to your linux-next included trees
until v4.9-rc1 has been released i.e. the merge window closes.
Changes since 20161013:
The akpm-current tree still had its build failures for which I applied
2 patches.
The akpm tree gained a conflict against the n
Hi all,
Please do not add any material intended for v3.19 to your linux-next
included trees until after v3.18-rc1 has been released.
Changes since 20141013:
Removed trees: powernv-cpuidle, signal-cleanup
Non-merge commits (relative to Linus' tree): 2254
2093 files changed, 71407 insertions(+),
On Tue, Oct 15, 2013 at 10:46:32AM +0200, Thierry Reding wrote:
> Oh wait, they were applied right after the merges that broke. I hadn't
> checked for that.
Yeah, it's because I've been doing incremental build checks - the builds
fail at the point the tree gets merged in.
signature.asc
Descript
On Mon, Oct 14, 2013 at 09:27:23PM +0100, Mark Brown wrote:
> On Mon, Oct 14, 2013 at 11:58:10AM -0700, Randy Dunlap wrote:
> > On 10/14/13 07:48, Thierry Reding wrote:
>
> > > Gained a few conflicts, but nothing too exciting. x86 and ARM default
> > > configurations build fine. There were some bu
On Mon, Oct 14, 2013 at 11:58:10AM -0700, Randy Dunlap wrote:
> On 10/14/13 07:48, Thierry Reding wrote:
> > Hi all,
> >
> > I've uploaded today's linux-next tree to the master branch of the
> > repository below:
> >
> > git://gitorious.org/thierryreding/linux-next.git
> >
> > A next-201
On 10/14/13 07:48, Thierry Reding wrote:
> Hi all,
>
> I've uploaded today's linux-next tree to the master branch of the
> repository below:
>
> git://gitorious.org/thierryreding/linux-next.git
>
> A next-20131014 tag is also provided for convenience.
>
> Gained a few conflicts, but not
On Mon, Oct 14, 2013 at 11:58:10AM -0700, Randy Dunlap wrote:
> On 10/14/13 07:48, Thierry Reding wrote:
> > Gained a few conflicts, but nothing too exciting. x86 and ARM default
> > configurations build fine. There were some build failures unrelated to
> Maybe you could build allmodconfig instea
On 10/14/13 07:48, Thierry Reding wrote:
> Hi all,
>
> I've uploaded today's linux-next tree to the master branch of the
> repository below:
>
> git://gitorious.org/thierryreding/linux-next.git
>
> A next-20131014 tag is also provided for convenience.
>
> Gained a few conflicts, but not
Hi all,
I've uploaded today's linux-next tree to the master branch of the
repository below:
git://gitorious.org/thierryreding/linux-next.git
A next-20131014 tag is also provided for convenience.
Gained a few conflicts, but nothing too exciting. x86 and ARM default
configurations build f
13 matches
Mail list logo
