On Tue, 5 May 2020 at 09:16, Stephen Rothwell wrote:
>
> Hi all,
>
> Changes since 20200504:
>
> New tree: ti-k3
>
> My fixes tree contains:
>
> bbefc924d0ff ("ubsan: disable UBSAN_ALIGNMENT under COMPILE_TEST")
> 7cb1d38f52b1 ("drm/msm: Fix undefined "rd_full" link error")
>
> The qcom tree s
Hi all,
Changes since 20200504:
New tree: ti-k3
My fixes tree contains:
bbefc924d0ff ("ubsan: disable UBSAN_ALIGNMENT under COMPILE_TEST")
7cb1d38f52b1 ("drm/msm: Fix undefined "rd_full" link error")
The qcom tree still had its build failure for which I reverted a commit.
Non-merge commit
Hi all,
Please do not add any v4.13 destined material in your linux-next
included branches until after v4.12-rc1 has been released.
Changes since 20170504:
The rdma tree gained a conflict against the pci tree.
The spi-nor tree lost its build failure.
Non-merge commits (relative to Linus' tree)
Hi all,
Changes since 20160504:
Dropped tree: hsi (at the maintainer's request)
The net-next tree gained a conflict against the net tree.
The borntraeger tree gained a conflict against the kvms390 tree.
Non-merge commits (relative to Linus' tree): 8189
7227 files changed, 309272 insertions(+)
Hi all,
Changes since 20150504:
New tree: coresight
Non-merge commits (relative to Linus' tree): 1771
1812 files changed, 92548 insertions(+), 38087 deletions(-)
I have created today's linux-next tree at
git://git.ke
On Mon, May 5, 2014 at 12:26 PM, Stephen Rothwell wrote:
> Hi Michael,
>
> On Mon, 5 May 2014 12:06:27 +0200 "Michael Kerrisk (man-pages)"
> wrote:
>>
>> Okay, must be my problem then. Sorry for the noise. Somehow, I'm not
>> syncing my linux-next correctly then. (Is the proper way of doing this
Hi Michael,
On Mon, 5 May 2014 12:06:27 +0200 "Michael Kerrisk (man-pages)"
wrote:
>
> Okay, must be my problem then. Sorry for the noise. Somehow, I'm not
> syncing my linux-next correctly then. (Is the proper way of doing this
> documented somewhere?)
Yeah, in the stuff you quoted :-)
"If yo
Hi Stephen,
On Mon, May 5, 2014 at 11:57 AM, Stephen Rothwell wrote:
> Hi Michael,
>
> On Mon, 5 May 2014 10:42:23 +0200 Michael Kerrisk
> wrote:
>>
>> I don't know what the process is for clearing cruft out of linux-next
>> is, but there's at least one piece of cruft that probably should go:
>
Hi Michael,
On Mon, 5 May 2014 10:42:23 +0200 Michael Kerrisk
wrote:
>
> I don't know what the process is for clearing cruft out of linux-next
> is, but there's at least one piece of cruft that probably should go:
I usually depend on maintainers to clean up their trees.
> commit d30c01a0611d54
Stephen,
I don't know what the process is for clearing cruft out of linux-next
is, but there's at least one piece of cruft that probably should go:
commit d30c01a0611d54926ac860721c933edafcc91905
commit 8c013e265a8eca0ada9f1aaa6cd7590698dc7231
commit e86263c9d00efb091a5215b9e4063378828d815c
(and
Hi all,
This tree still fails (more than usual) the powerpc allyesconfig build
and also the celleb_defconfig.
Changes since 20140502:
The powerpc tree still had its build failure.
The net-next tree gained a conflict against the net tree.
The tip tree gained a conflict against the net-next tree
11 matches
Mail list logo
