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
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
6 matches
Mail list logo
