mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-s390 <linux-s390@vger.kernel.org>,
	Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [GIT PULL] s390 patches for the 4.17 merge window #1
Date: Mon, 9 Apr 2018 15:18:21 +0200	[thread overview]
Message-ID: <20180409151821.2d92303f@mschwideX1> (raw)
In-Reply-To: <20180403111242.49f43ee7@mschwideX1>

Hi Linus,

On Tue, 3 Apr 2018 11:12:42 +0200
Martin Schwidefsky <schwidefsky@de.ibm.com> wrote:

> please pull from the 'for-linus' branch of
> 
> 	git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus
> 
> to receive the following updates:
> 
>  * Improvements for the spectre defense:
>    - The spectre related code is consolidated to a single file nospec-branch.c
>    - Automatic enable/disable for the spectre v2 defenses (expoline vs. nobp)
>    - Syslog messages for specve v2 are added
>    - Enable CONFIG_GENERIC_CPU_VULNERABILITIES and define the attribute
>      functions for spectre v1 and v2
> 
>  * Add helper macros for assembler alternatives and use them to shorten
>    the code in entry.S.
> 
>  * Add support for persistent configuration data via the SCLP Store Data
>    interface. The H/W interface requires a page table that uses 4K pages
>    only, the code to setup such an address space is added as well.
> 
>  * Enable virtio GPU emulation in QEMU. To do this the depends statements
>    for a few common Kconfig options are modified.
> 
>  * Add support for format-3 channel path descriptors and add a binary
>    sysfs interface to export the associated utility strings.
> 
>  * Add a sysfs attribute to control the IFCC handling in case of constant
>    channel errors.
> 
>  * The vfio-ccw changes from Cornelia.
> 
>  * Bug fixes and cleanups.
> 
> There is a trivial merge conflict in drivers/video/console/Kconfig.

Ping.

Did this please-pull get lost or is there a deeper reason that prevents
the upstream integration?

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

  reply	other threads:[~2018-04-09 13:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-03  9:12 Martin Schwidefsky
2018-04-09 13:18 ` Martin Schwidefsky [this message]
2018-04-09 16:07   ` Linus Torvalds
2018-04-09 16:22     ` Martin Schwidefsky
2018-04-09 16:40       ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180409151821.2d92303f@mschwideX1 \
    --to=schwidefsky@de.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®