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 +0200
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 S
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, Zhan
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, a
> 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 othe
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 s
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: er
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) \
^
security
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, than
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.
http://git.kernel.org/?p=linux/kernel/git/sfr/linux-ne
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]
http://www.canb.auug.org.au/
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 linux-a
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 k
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. Ther
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? Ag
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
git://git.kernel.org/pub/scm/linux/k
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 ar
20 matches
Mail list logo
