Hi all,
Changes since 20190319:
The amdgpu tree still had its build failure for which I reverted a commit.
The selinux tree lost its build failure.
The scsi tree gained a build failure for which I applied a patch.
Non-merge commits (relative to Linus' tree): 1993
1658 files changed, 57917
Hi all,
Changes since 20180319:
The vfs tree still had its build failure for which I reverted a commit.
The drm-misc tree gained a conflict against Linus' tree.
Non-merge commits (relative to Linus' tree): 8417
10910 files changed, 369623 insertions(+), 737452 deletions(-)
Hi all,
Changes since 20180319:
The vfs tree still had its build failure for which I reverted a commit.
The drm-misc tree gained a conflict against Linus' tree.
Non-merge commits (relative to Linus' tree): 8417
10910 files changed, 369623 insertions(+), 737452 deletions(-)
Hi all,
Changes since 20170310:
Changed trees: kbuild-currrent, kbuild (new maintainer)
The renesas tree gained a conflict against the arm tree.
The fscrypt tree gained a conflict against Linus' tree.
The net-next tree gained a conflict against the net tree.
The tty tree gained a conflict
Hi all,
Changes since 20170310:
Changed trees: kbuild-currrent, kbuild (new maintainer)
The renesas tree gained a conflict against the arm tree.
The fscrypt tree gained a conflict against Linus' tree.
The net-next tree gained a conflict against the net tree.
The tty tree gained a conflict
Hi all,
Changes since 20150319:
The vfs tree still had its build failure for which I applied a patch.
The battery tree gained a conflict against the hid tree.
The spi tree gained a conflict against the jc_docs tree.
Non-merge commits (relative to Linus' tree): 5204
4973 files changed, 225035
Hi all,
Changes since 20150319:
The vfs tree still had its build failure for which I applied a patch.
The battery tree gained a conflict against the hid tree.
The spi tree gained a conflict against the jc_docs tree.
Non-merge commits (relative to Linus' tree): 5204
4973 files changed, 225035
Hi all,
This tree still fails (more than usual) the powerpc allyesconfig build.
Changes since 20140319:
The powerpc tree still had its build failure.
The net-next tree lost its another build failure.
The wireless-next tree lost its build failure.
The drm-intel tree lost its build failure.
Hi all,
This tree still fails (more than usual) the powerpc allyesconfig build.
Changes since 20140319:
The powerpc tree still had its build failure.
The net-next tree lost its another build failure.
The wireless-next tree lost its build failure.
The drm-intel tree lost its build failure.
Hi David,
On Wed, 20 Mar 2013 19:49:09 -0700 (PDT) David Rientjes
wrote:
>
> On Thu, 21 Mar 2013, Stephen Rothwell wrote:
>
> > What exactly are "these patches" so that I can remove them from my copy
> > of the mmotm tree (assuming that Andrew does not get a new mmotm released
> > in the next
On Thu, 21 Mar 2013, Stephen Rothwell wrote:
> What exactly are "these patches" so that I can remove them from my copy
> of the mmotm tree (assuming that Andrew does not get a new mmotm released
> in the next hour or so).
>
[nacked]
Hi,
On Wed, 20 Mar 2013 17:10:30 -0700 (PDT) David Rientjes
wrote:
>
> On Wed, 20 Mar 2013, David Rientjes wrote:
>
> > I don't think that's it, linux/kexec.h already gets included indirectly.
> > The problem is that CONFIG_KEXEC isn't set so the definition in kexec.h is
> > meaningless.
>
On Wed, 20 Mar 2013, David Rientjes wrote:
> I don't think that's it, linux/kexec.h already gets included indirectly.
> The problem is that CONFIG_KEXEC isn't set so the definition in kexec.h is
> meaningless.
>
> This comes from "vmcore: check NT_VMCORE_PAD as a mark indicating the end
> of
On 03/20/13 11:56, David Rientjes wrote:
> On Wed, 20 Mar 2013, Randy Dunlap wrote:
>
>> on x86_64:
>>
>> fs/proc/vmcore.c: In function 'merge_note_headers_elf64':
>> fs/proc/vmcore.c:349:22: error: 'VMCOREINFO_NOTE_NAME' undeclared (first use
>> in this function)
>> fs/proc/vmcore.c:349:22:
On Wed, 20 Mar 2013, Randy Dunlap wrote:
> on x86_64:
>
> fs/proc/vmcore.c: In function 'merge_note_headers_elf64':
> fs/proc/vmcore.c:349:22: error: 'VMCOREINFO_NOTE_NAME' undeclared (first use
> in this function)
> fs/proc/vmcore.c:349:22: note: each undeclared identifier is reported only
>
On Wed, 20 Mar 2013, Randy Dunlap wrote:
on x86_64:
fs/proc/vmcore.c: In function 'merge_note_headers_elf64':
fs/proc/vmcore.c:349:22: error: 'VMCOREINFO_NOTE_NAME' undeclared (first use
in this function)
fs/proc/vmcore.c:349:22: note: each undeclared identifier is reported only
once
On 03/20/13 11:56, David Rientjes wrote:
On Wed, 20 Mar 2013, Randy Dunlap wrote:
on x86_64:
fs/proc/vmcore.c: In function 'merge_note_headers_elf64':
fs/proc/vmcore.c:349:22: error: 'VMCOREINFO_NOTE_NAME' undeclared (first use
in this function)
fs/proc/vmcore.c:349:22: note: each
On Wed, 20 Mar 2013, David Rientjes wrote:
I don't think that's it, linux/kexec.h already gets included indirectly.
The problem is that CONFIG_KEXEC isn't set so the definition in kexec.h is
meaningless.
This comes from vmcore: check NT_VMCORE_PAD as a mark indicating the end
of ELF
Hi,
On Wed, 20 Mar 2013 17:10:30 -0700 (PDT) David Rientjes rient...@google.com
wrote:
On Wed, 20 Mar 2013, David Rientjes wrote:
I don't think that's it, linux/kexec.h already gets included indirectly.
The problem is that CONFIG_KEXEC isn't set so the definition in kexec.h is
On Thu, 21 Mar 2013, Stephen Rothwell wrote:
What exactly are these patches so that I can remove them from my copy
of the mmotm tree (assuming that Andrew does not get a new mmotm released
in the next hour or so).
[nacked]
Hi David,
On Wed, 20 Mar 2013 19:49:09 -0700 (PDT) David Rientjes rient...@google.com
wrote:
On Thu, 21 Mar 2013, Stephen Rothwell wrote:
What exactly are these patches so that I can remove them from my copy
of the mmotm tree (assuming that Andrew does not get a new mmotm released
in
Hi Sedat,
On Wed, 20 Mar 2013 06:44:45 +0100 Sedat Dilek wrote:
>
> again I can read this offline before I have received it online (in my
> Gmail-account).
> Why shall I subscribe a ML when I am faster reading it offline?
> Whom to contact in such a case (ML-admin)?
Probably
Hi all,
Changes since 20130319:
The cgroup tree regained its build failure for which I have reverted a
commit.
The tty tree gained 2 build failures so I used the version from
next-20130319.
The char-misc tree lost its build failure.
The gpio tree still had its build failure for which I
Hi all,
Changes since 20130319:
The cgroup tree regained its build failure for which I have reverted a
commit.
The tty tree gained 2 build failures so I used the version from
next-20130319.
The char-misc tree lost its build failure.
The gpio tree still had its build failure for which I
Hi Sedat,
On Wed, 20 Mar 2013 06:44:45 +0100 Sedat Dilek sedat.di...@gmail.com wrote:
again I can read this offline before I have received it online (in my
Gmail-account).
Why shall I subscribe a ML when I am faster reading it offline?
Whom to contact in such a case (ML-admin)?
Probably
25 matches
Mail list logo
