linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: torvalds@linux-foundation.org
Cc: linux-um@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] UML changes for 4.21
Date: Wed, 02 Jan 2019 23:52:26 +0100	[thread overview]
Message-ID: <1590974.xBRWhrZ5gH@blindfold> (raw)

Linus,

The following changes since commit 8fe28cb58bcb235034b64cbbb7550a8a43fd88be:

  Linux 4.20 (2018-12-23 15:55:59 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git for-linus-4.21-rc1

for you to fetch changes up to 940b241d9050fc354f68c182e99fc3da1ff36bc0:

  um: Remove obsolete reenable_XX calls (2018-12-27 22:48:35 +0100)

----------------------------------------------------------------
Thiss pull requests contains UML updates for 4.21:

- DISCARD support for our block device driver
- Many TLB flush optimizations
- Various smaller fixes
- And most important, Anton agreed to help me maintaining UML

----------------------------------------------------------------
Anton Ivanov (11):
      um: Switch to block-mq constants in the UML UBD driver
      um: Clean-up command processing in UML UBD driver
      um: Remove unsafe printks from the io thread
      um: Add support for DISCARD in the UBD Driver
      um: Remove unnecessary faulted check in uaccess.c
      um: Optimize TLB operations v2
      um: Skip TLB flushing where not needed
      um: Avoid marking pages with "changed protection"
      um: Optimize Flush TLB for force/fork case
      Add Anton Ivanov to UML maintainers
      um: Remove obsolete reenable_XX calls

Christoph Hellwig (1):
      um: writev needs <sys/uio.h>

Hernán Gonzalez (1):
      um: Add HAVE_DEBUG_BUGVERBOSE

Masahiro Yamada (1):
      um: remove redundant generic-y

Richard Weinberger (3):
      um: Update maintainers file entry
      um: Include sys/uio.h to have writev()
      um: Make GCOV depend on !KCOV

 MAINTAINERS                       |   3 +-
 arch/um/Kconfig                   |   1 +
 arch/um/Kconfig.debug             |   1 +
 arch/um/drivers/chan_kern.c       |  10 --
 arch/um/drivers/line.c            |  10 --
 arch/um/drivers/mconsole_kern.c   |   2 -
 arch/um/drivers/net_kern.c        |   2 -
 arch/um/drivers/port_kern.c       |   1 -
 arch/um/drivers/random.c          |   1 -
 arch/um/drivers/ubd_kern.c        | 231 ++++++++++++++++++++++++--------------
 arch/um/drivers/vector_user.c     |   2 +
 arch/um/include/asm/Kbuild        |   2 -
 arch/um/include/asm/pgtable.h     |   9 +-
 arch/um/include/shared/irq_user.h |   1 -
 arch/um/include/shared/os.h       |   1 +
 arch/um/kernel/irq.c              |   6 -
 arch/um/kernel/sigio.c            |   1 -
 arch/um/kernel/skas/uaccess.c     |  23 ++--
 arch/um/kernel/tlb.c              | 115 ++++++++++++-------
 arch/um/os-Linux/file.c           |  10 ++
 20 files changed, 259 insertions(+), 173 deletions(-)




             reply	other threads:[~2019-01-02 22:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-02 22:52 Richard Weinberger [this message]
2019-01-03  3:05 ` [GIT PULL] UML changes for 4.21 pr-tracker-bot

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=1590974.xBRWhrZ5gH@blindfold \
    --to=richard@nod.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-um@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).