On Thu, 21 Feb 2019 at 09:04, Geert Uytterhoeven wrote:
>
> Hi Shaokun,
>
> On Thu, Feb 21, 2019 at 1:45 AM Zhangshaokun
> wrote:
> > On 2019/2/20 18:05, Ard Biesheuvel wrote:
> > > On Wed, 20 Feb 2019 at 10:58, Jarkko Sakkinen
> > > wrote:
> > >>
> > >> On Wed, Feb 20, 2019 at 11:52:52AM
Hi Geert,
On 2019/2/21 16:03, Geert Uytterhoeven wrote:
> Hi Shaokun,
>
> On Thu, Feb 21, 2019 at 1:45 AM Zhangshaokun
> wrote:
>> On 2019/2/20 18:05, Ard Biesheuvel wrote:
>>> On Wed, 20 Feb 2019 at 10:58, Jarkko Sakkinen
>>> wrote:
On Wed, Feb 20, 2019 at 11:52:52AM +0200, Jarkko
Hi Shaokun,
On Thu, Feb 21, 2019 at 1:45 AM Zhangshaokun wrote:
> On 2019/2/20 18:05, Ard Biesheuvel wrote:
> > On Wed, 20 Feb 2019 at 10:58, Jarkko Sakkinen
> > wrote:
> >>
> >> On Wed, Feb 20, 2019 at 11:52:52AM +0200, Jarkko Sakkinen wrote:
> >>> On Wed, Feb 20, 2019 at 05:11:15PM +0800,
Hi Ard,
On 2019/2/20 18:05, Ard Biesheuvel wrote:
> On Wed, 20 Feb 2019 at 10:58, Jarkko Sakkinen
> wrote:
>>
>> On Wed, Feb 20, 2019 at 11:52:52AM +0200, Jarkko Sakkinen wrote:
>>> On Wed, Feb 20, 2019 at 05:11:15PM +0800, Zhangshaokun wrote:
There is a compiler failure on arm64 platform,
> Fixes for this have already been proposed, and should appear in -next shortly
>
> The EFI one is here
> https://mail.google.com/mail/u/0/#label/linux-efi/FMfcgxwBVgrQRjglPkWRqRqVclGgVDnB
>
> Not sure about the IMA one, Mimi should be able to comment ...
I've already commented on the
On Wed, 20 Feb 2019 at 10:58, Jarkko Sakkinen
wrote:
>
> On Wed, Feb 20, 2019 at 11:52:52AM +0200, Jarkko Sakkinen wrote:
> > On Wed, Feb 20, 2019 at 05:11:15PM +0800, Zhangshaokun wrote:
> > > There is a compiler failure on arm64 platform, as follow:
> > >
> > > AS arch/arm64/kvm/hyp.o
>
On Wed, Feb 20, 2019 at 11:52:52AM +0200, Jarkko Sakkinen wrote:
> On Wed, Feb 20, 2019 at 05:11:15PM +0800, Zhangshaokun wrote:
> > There is a compiler failure on arm64 platform, as follow:
> >
> > AS arch/arm64/kvm/hyp.o
> > CC kernel/trace/ring_buffer.o
> > In file included from
On Wed, Feb 20, 2019 at 05:11:15PM +0800, Zhangshaokun wrote:
> There is a compiler failure on arm64 platform, as follow:
>
> AS arch/arm64/kvm/hyp.o
> CC kernel/trace/ring_buffer.o
> In file included from security/integrity/ima/ima_fs.c:30:0:
> security/integrity/ima/ima.h:176:7:
There is a compiler failure on arm64 platform, as follow:
AS arch/arm64/kvm/hyp.o
CC kernel/trace/ring_buffer.o
In file included from security/integrity/ima/ima_fs.c:30:0:
security/integrity/ima/ima.h:176:7: error: redeclaration of enumerator ‘NONE’
hook(NONE) \
^
Hi all,
Changes since 20190219:
The asm-generic tree lost its build failure.
The v4l-dvb tree lost its build failure.
The net-next tree gained a conflict against the bpf tree.
The kvm tree still had its build failure so I used a supplied patch.
The akpm-current tree gained a build failure
Hi all,
Changes since 20180219:
The sound-asoc tree lost its build failures.
Non-merge commits (relative to Linus' tree): 2441
2914 files changed, 105361 insertions(+), 55486 deletions(-)
I have created today's
Hi all,
Changes since 20180219:
The sound-asoc tree lost its build failures.
Non-merge commits (relative to Linus' tree): 2441
2914 files changed, 105361 insertions(+), 55486 deletions(-)
I have created today's
Hi all,
Changes since 20170217:
The pci tree gained a conflict (probably) against Linus' tree.
The kspp tree gained a conflict against the net-next tree.
The tip tree gained a conflict against the net-next tree.
The target-bva tree gained conflicts against the target-updates tree.
Non-merge
Hi all,
Changes since 20170217:
The pci tree gained a conflict (probably) against Linus' tree.
The kspp tree gained a conflict against the net-next tree.
The tip tree gained a conflict against the net-next tree.
The target-bva tree gained conflicts against the target-updates tree.
Non-merge
Hi all,
Please do not add any material destined for v3.21 to your linux-next
included trees until after v3.20-rc1 has been released.
Changes since 20150219:
The clk tree gained a conflict against Linus' tree.
Non-merge commits (relative to Linus' tree): 1232
870 files changed, 32474
Hi all,
Please do not add any material destined for v3.21 to your linux-next
included trees until after v3.20-rc1 has been released.
Changes since 20150219:
The clk tree gained a conflict against Linus' tree.
Non-merge commits (relative to Linus' tree): 1232
870 files changed, 32474
Hi all,
If you see failures in building this tree due to missing declarations of
k..alloc/free, then it may be caused by commit 2bd59d48ebfb ("cgroup:
convert to kernfs"). Please send Tejun Heo a patch
adding an inclusion of linux/slab.h to the appropriate file(s).
This tree fails (more than
Hi all,
If you see failures in building this tree due to missing declarations of
k..alloc/free, then it may be caused by commit 2bd59d48ebfb (cgroup:
convert to kernfs). Please send Tejun Heo t...@kernel.org a patch
adding an inclusion of linux/slab.h to the appropriate file(s).
This tree fails
On Thu, 2008-02-21 at 02:20 +1100, Stephen Rothwell wrote:
> Hi James,
>
> On Wed, 20 Feb 2008 08:59:20 -0600 James Bottomley <[EMAIL PROTECTED]> wrote:
> >
> > Is the merge log available anywhere yet?
>
> Are you looking for more that what is in Next/merge.log in the tree?
Yes, that's it,
James Bottomley wrote:
> On Wed, 2008-02-20 at 16:34 +1100, Stephen Rothwell wrote:
>> There were no merge conflicts and only one build failure!
>
> Is the merge log available anywhere yet?
Yes, there is the Next/merge.log file in linux-next.
Hi James,
On Wed, 20 Feb 2008 08:59:20 -0600 James Bottomley <[EMAIL PROTECTED]> wrote:
>
> Is the merge log available anywhere yet?
Are you looking for more that what is in Next/merge.log in the tree?
--
Cheers,
Stephen Rothwell[EMAIL PROTECTED]
On Wed, 2008-02-20 at 16:34 +1100, Stephen Rothwell wrote:
> Hi all,
>
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
>
> You can see which trees have been included by looking in the Next/Trees
> file in the source. There are also
On Wed, Feb 20, 2008 at 04:34:57PM +1100, Stephen Rothwell wrote:
>...
> I will stop making these announcements now unless there is some change to
> the tree or things people should know. There should be a new tree every
> (Australian Capital Territory) working day.
I'd recommend removing
On Wed, Feb 20, 2008 at 04:34:57PM +1100, Stephen Rothwell wrote:
...
I will stop making these announcements now unless there is some change to
the tree or things people should know. There should be a new tree every
(Australian Capital Territory) working day.
I'd recommend removing linux-arch
On Wed, 2008-02-20 at 16:34 +1100, Stephen Rothwell wrote:
Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also
James Bottomley wrote:
On Wed, 2008-02-20 at 16:34 +1100, Stephen Rothwell wrote:
There were no merge conflicts and only one build failure!
Is the merge log available anywhere yet?
Yes, there is the Next/merge.log file in linux-next.
On Thu, 2008-02-21 at 02:20 +1100, Stephen Rothwell wrote:
Hi James,
On Wed, 20 Feb 2008 08:59:20 -0600 James Bottomley [EMAIL PROTECTED] wrote:
Is the merge log available anywhere yet?
Are you looking for more that what is in Next/merge.log in the tree?
Yes, that's it, thanks!
James
Stephen Rothwell wrote:
> That would work. Chris has the right idea, though. Just set up
> linux-next as a remote on any existing clone of Linus' tree and the
> "fetch" will forcibly update the linux-next/master branch (remember to
> not have that branch checked out when you fetch).
>
> If you
Greg KH wrote:
On Wed, Feb 20, 2008 at 04:34:57PM +1100, Stephen Rothwell wrote:
Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source.
Hi Greg,
On Tue, 19 Feb 2008 21:50:55 -0800 Greg KH <[EMAIL PROTECTED]> wrote:
>
> What's the best way to constantly follow this tree? I had cloned it a
> while ago, but now if I 'git pull' it wants to merge things, which isn't
> right.
>
> I'm guessing that this is constantly being rebased?
On Tue, Feb 19, 2008 at 09:50:55PM -0800, Greg KH wrote:
> What's the best way to constantly follow this tree? I had cloned it
> a while ago, but now if I 'git pull' it wants to merge things, which
> isn't right.
I would guess:
$ git remote add linux-next
From: Greg KH <[EMAIL PROTECTED]>
Date: Tue, 19 Feb 2008 21:50:55 -0800
> On Wed, Feb 20, 2008 at 04:34:57PM +1100, Stephen Rothwell wrote:
> > I will stop making these announcements now unless there is some change to
> > the tree or things people should know. There should be a new tree every
>
On Wed, Feb 20, 2008 at 04:34:57PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
>
> You can see which trees have been included by looking in the Next/Trees
> file in the source. There
Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between
Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between
On Tue, Feb 19, 2008 at 09:50:55PM -0800, Greg KH wrote:
What's the best way to constantly follow this tree? I had cloned it
a while ago, but now if I 'git pull' it wants to merge things, which
isn't right.
I would guess:
$ git remote add linux-next
On Wed, Feb 20, 2008 at 04:34:57PM +1100, Stephen Rothwell wrote:
Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also
From: Greg KH [EMAIL PROTECTED]
Date: Tue, 19 Feb 2008 21:50:55 -0800
On Wed, Feb 20, 2008 at 04:34:57PM +1100, Stephen Rothwell wrote:
I will stop making these announcements now unless there is some change to
the tree or things people should know. There should be a new tree every
Hi Greg,
On Tue, 19 Feb 2008 21:50:55 -0800 Greg KH [EMAIL PROTECTED] wrote:
What's the best way to constantly follow this tree? I had cloned it a
while ago, but now if I 'git pull' it wants to merge things, which isn't
right.
I'm guessing that this is constantly being rebased? Against
Greg KH wrote:
On Wed, Feb 20, 2008 at 04:34:57PM +1100, Stephen Rothwell wrote:
Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source.
Stephen Rothwell wrote:
That would work. Chris has the right idea, though. Just set up
linux-next as a remote on any existing clone of Linus' tree and the
fetch will forcibly update the linux-next/master branch (remember to
not have that branch checked out when you fetch).
If you keep a
41 matches
Mail list logo
