On Wed, 25 Jul 2018 12:40:26 -0700
Kees Cook wrote:
> On Tue, Jul 24, 2018 at 12:24 AM, Martin Schwidefsky
> wrote:
> > On Tue, 24 Jul 2018 09:15:58 +0200
> > Christian Borntraeger wrote:
> >
> >> On 07/24/2018 08:18 AM, Martin Schwidefsky wrote:
> >> > On Mon, 23 Jul 2018 16:17:22 -0700
>
On Wed, 25 Jul 2018 12:40:26 -0700
Kees Cook wrote:
> On Tue, Jul 24, 2018 at 12:24 AM, Martin Schwidefsky
> wrote:
> > On Tue, 24 Jul 2018 09:15:58 +0200
> > Christian Borntraeger wrote:
> >
> >> On 07/24/2018 08:18 AM, Martin Schwidefsky wrote:
> >> > On Mon, 23 Jul 2018 16:17:22 -0700
>
On Tue, Jul 24, 2018 at 12:24 AM, Martin Schwidefsky
wrote:
> On Tue, 24 Jul 2018 09:15:58 +0200
> Christian Borntraeger wrote:
>
>> On 07/24/2018 08:18 AM, Martin Schwidefsky wrote:
>> > On Mon, 23 Jul 2018 16:17:22 -0700
>> > Linus Torvalds wrote:
>> >
>> >> On Mon, Jul 23, 2018 at 2:23 PM
On Tue, Jul 24, 2018 at 12:24 AM, Martin Schwidefsky
wrote:
> On Tue, 24 Jul 2018 09:15:58 +0200
> Christian Borntraeger wrote:
>
>> On 07/24/2018 08:18 AM, Martin Schwidefsky wrote:
>> > On Mon, 23 Jul 2018 16:17:22 -0700
>> > Linus Torvalds wrote:
>> >
>> >> On Mon, Jul 23, 2018 at 2:23 PM
On 07/24/2018 09:24 AM, Martin Schwidefsky wrote:
> On Tue, 24 Jul 2018 09:15:58 +0200
> Christian Borntraeger wrote:
>
>> On 07/24/2018 08:18 AM, Martin Schwidefsky wrote:
>>> On Mon, 23 Jul 2018 16:17:22 -0700
>>> Linus Torvalds wrote:
>>>
On Mon, Jul 23, 2018 at 2:23 PM Guenter
On 07/24/2018 09:24 AM, Martin Schwidefsky wrote:
> On Tue, 24 Jul 2018 09:15:58 +0200
> Christian Borntraeger wrote:
>
>> On 07/24/2018 08:18 AM, Martin Schwidefsky wrote:
>>> On Mon, 23 Jul 2018 16:17:22 -0700
>>> Linus Torvalds wrote:
>>>
On Mon, Jul 23, 2018 at 2:23 PM Guenter
On Tue, 24 Jul 2018 09:15:58 +0200
Christian Borntraeger wrote:
> On 07/24/2018 08:18 AM, Martin Schwidefsky wrote:
> > On Mon, 23 Jul 2018 16:17:22 -0700
> > Linus Torvalds wrote:
> >
> >> On Mon, Jul 23, 2018 at 2:23 PM Guenter Roeck wrote:
> >>>
>
> Martin - can we just
On Tue, 24 Jul 2018 09:15:58 +0200
Christian Borntraeger wrote:
> On 07/24/2018 08:18 AM, Martin Schwidefsky wrote:
> > On Mon, 23 Jul 2018 16:17:22 -0700
> > Linus Torvalds wrote:
> >
> >> On Mon, Jul 23, 2018 at 2:23 PM Guenter Roeck wrote:
> >>>
>
> Martin - can we just
On 07/24/2018 08:18 AM, Martin Schwidefsky wrote:
> On Mon, 23 Jul 2018 16:17:22 -0700
> Linus Torvalds wrote:
>
>> On Mon, Jul 23, 2018 at 2:23 PM Guenter Roeck wrote:
>>>
Martin - can we just remove the
select HAVE_GCC_PLUGINS
from the s390 Kconfig
On 07/24/2018 08:18 AM, Martin Schwidefsky wrote:
> On Mon, 23 Jul 2018 16:17:22 -0700
> Linus Torvalds wrote:
>
>> On Mon, Jul 23, 2018 at 2:23 PM Guenter Roeck wrote:
>>>
Martin - can we just remove the
select HAVE_GCC_PLUGINS
from the s390 Kconfig
On Mon, 23 Jul 2018 16:17:22 -0700
Linus Torvalds wrote:
> On Mon, Jul 23, 2018 at 2:23 PM Guenter Roeck wrote:
> >
> > >
> > > Martin - can we just remove the
> > >
> > > select HAVE_GCC_PLUGINS
> > >
> > > from the s390 Kconfig file (or perhaps add "if BROKEN" or something to
> > >
On Mon, 23 Jul 2018 16:17:22 -0700
Linus Torvalds wrote:
> On Mon, Jul 23, 2018 at 2:23 PM Guenter Roeck wrote:
> >
> > >
> > > Martin - can we just remove the
> > >
> > > select HAVE_GCC_PLUGINS
> > >
> > > from the s390 Kconfig file (or perhaps add "if BROKEN" or something to
> > >
On Mon, Jul 23, 2018 at 2:23 PM Guenter Roeck wrote:
>
> >
> > Martin - can we just remove the
> >
> > select HAVE_GCC_PLUGINS
> >
> > from the s390 Kconfig file (or perhaps add "if BROKEN" or something to
> > disable it).
> >
> > Because if it's not getting fixed, it shouldn't be
On Mon, Jul 23, 2018 at 2:23 PM Guenter Roeck wrote:
>
> >
> > Martin - can we just remove the
> >
> > select HAVE_GCC_PLUGINS
> >
> > from the s390 Kconfig file (or perhaps add "if BROKEN" or something to
> > disable it).
> >
> > Because if it's not getting fixed, it shouldn't be
On Mon, Jul 23, 2018 at 2:23 PM Guenter Roeck wrote:
>
> My patch is also at
>
> https://patchwork.ozlabs.org/patch/937283/
Ah, ok, so that just adds the forward-declaration of 'struct page' in
the right global namespace.
Anyway, I'll just re-order the includes as I suggested, which I think
is
On Mon, Jul 23, 2018 at 2:23 PM Guenter Roeck wrote:
>
> My patch is also at
>
> https://patchwork.ozlabs.org/patch/937283/
Ah, ok, so that just adds the forward-declaration of 'struct page' in
the right global namespace.
Anyway, I'll just re-order the includes as I suggested, which I think
is
On Mon, Jul 23, 2018 at 01:56:15PM -0700, Linus Torvalds wrote:
> Adding davem for the sparc issue, Martin for the s390 one.
>
> On Mon, Jul 23, 2018 at 1:46 PM Guenter Roeck wrote:
> >
> > The s390 gcc plugins related build error reported previously has not really
> > been fixed; after feedback
On Mon, Jul 23, 2018 at 01:56:15PM -0700, Linus Torvalds wrote:
> Adding davem for the sparc issue, Martin for the s390 one.
>
> On Mon, Jul 23, 2018 at 1:46 PM Guenter Roeck wrote:
> >
> > The s390 gcc plugins related build error reported previously has not really
> > been fixed; after feedback
From: Linus Torvalds
Date: Mon, 23 Jul 2018 13:56:15 -0700
> Hmm. I assume it's
>
> arch/sparc/include/asm/cacheflush_32.h
>
> that wants a forward-declaration of 'struct page', and doesn't include
> any header files.
>
> The fix is presumably to move the
>
>#include
>
> in
From: Linus Torvalds
Date: Mon, 23 Jul 2018 13:56:15 -0700
> Hmm. I assume it's
>
> arch/sparc/include/asm/cacheflush_32.h
>
> that wants a forward-declaration of 'struct page', and doesn't include
> any header files.
>
> The fix is presumably to move the
>
>#include
>
> in
Adding davem for the sparc issue, Martin for the s390 one.
On Mon, Jul 23, 2018 at 1:46 PM Guenter Roeck wrote:
>
> The s390 gcc plugins related build error reported previously has not really
> been fixed; after feedback from the s390 maintainers, suggesting that it
> won't get fixed in 4.18, I
Adding davem for the sparc issue, Martin for the s390 one.
On Mon, Jul 23, 2018 at 1:46 PM Guenter Roeck wrote:
>
> The s390 gcc plugins related build error reported previously has not really
> been fixed; after feedback from the s390 maintainers, suggesting that it
> won't get fixed in 4.18, I
On Sun, Jul 22, 2018 at 02:23:39PM -0700, Linus Torvalds wrote:
> So this was the week when the other shoe dropped ... The reason the
> two previous rc releases were so nice and small was that David hadn't
> sent me much networking fixes, and they came in this week.
>
Build results:
On Sun, Jul 22, 2018 at 02:23:39PM -0700, Linus Torvalds wrote:
> So this was the week when the other shoe dropped ... The reason the
> two previous rc releases were so nice and small was that David hadn't
> sent me much networking fixes, and they came in this week.
>
Build results:
mm: make vm_area_dup() actually copy the old vma data
mm: make vm_area_alloc() initialize core fields
Linux 4.18-rc6
Liran Alon (1):
KVM: VMX: Mark VMXArea with revision_id of physical CPU even
when eVMCS enabled
Lorenzo Colitti (1):
net: diag: Don't double-free TCP_NE
mm: make vm_area_dup() actually copy the old vma data
mm: make vm_area_alloc() initialize core fields
Linux 4.18-rc6
Liran Alon (1):
KVM: VMX: Mark VMXArea with revision_id of physical CPU even
when eVMCS enabled
Lorenzo Colitti (1):
net: diag: Don't double-free TCP_NE
Linus,
The following changes since commit 786b71f5b754273ccef6d9462e52062b3e1f9877:
Merge tag 'nds32-for-linus-4.17-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/greentime/linux (2018-05-28
05:25:57 -0700)
are available in the git repository at:
Linus,
The following changes since commit 786b71f5b754273ccef6d9462e52062b3e1f9877:
Merge tag 'nds32-for-linus-4.17-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/greentime/linux (2018-05-28
05:25:57 -0700)
are available in the git repository at:
28 matches
Mail list logo
