mbox series

[GIT,PULL] UML changes for 4.20-rc1

Message ID 1829585.6m1bt7BjAO@blindfold
State Accepted, archived
Headers show
Series [GIT,PULL] UML changes for 4.20-rc1 | expand

Pull-request

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

Message

Richard Weinberger Oct. 31, 2018, 9:22 p.m. UTC
Linus,

First of all, welcome back!

Please note that the vast majority of these changes have
been in -next since 4.18.
Due to vacation and other troubles I didn't send a pull request
back then.
I rebased them a few days ago on top of 4.19.

The following changes since commit 84df9525b0c27f3ebc2ebb1864fa62a97fdedb7d:

  Linux 4.19 (2018-10-22 07:37:37 +0100)

are available in the Git repository at:

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

for you to fetch changes up to 917e2fd2c53eb3c4162f5397555cbd394390d4bc:

  um: Make line/tty semantics use true write IRQ (2018-10-29 22:34:16 +0100)

----------------------------------------------------------------
This pull request contains the following updates for UML:

- Removal of old and dead code
- A bug fix for our tty driver
- Other minor cleanups across the code base
----------------------------------------------------------------

Anton Ivanov (1):
      um: Make line/tty semantics use true write IRQ

Christoph Hellwig (1):
      um: remove unused AIO code

Colin Ian King (1):
      um: trap: fix spelling mistake, EACCESS -> EACCES

Richard Weinberger (3):
      um: Drop own definition of PTRACE_SYSEMU/_SINGLESTEP
      um: Remove update_debugregs()
      um: Give start_idle_thread() a return code

Ritesh Raj Sarraf (1):
      um: Don't hardcode path as it is architecture dependent

YueHaibing (1):
      um: NULL check before kfree is not needed

 arch/um/drivers/line.c                |   4 +-
 arch/um/drivers/port_user.c           |   2 +-
 arch/um/drivers/vector_kern.c         |  15 +-
 arch/um/drivers/vector_user.c         |   6 +-
 arch/um/include/shared/aio.h          |  28 ---
 arch/um/kernel/irq.c                  |   3 +-
 arch/um/kernel/trap.c                 |   2 +-
 arch/um/os-Linux/Makefile             |   8 +-
 arch/um/os-Linux/aio.c                | 390 ----------------------------------
 arch/um/os-Linux/skas/process.c       |   5 +
 arch/x86/um/shared/sysdep/ptrace_32.h |  12 --
 11 files changed, 19 insertions(+), 456 deletions(-)
 delete mode 100644 arch/um/include/shared/aio.h
 delete mode 100644 arch/um/os-Linux/aio.c

Comments

Linus Torvalds Oct. 31, 2018, 10:48 p.m. UTC | #1
On Wed, Oct 31, 2018 at 2:22 PM Richard Weinberger <richard@nod.at> wrote:
>
> - Removal of old and dead code
> - A bug fix for our tty driver
> - Other minor cleanups across the code base

Pulled. I may not like recent rebases, but I do like this:

>  11 files changed, 19 insertions(+), 456 deletions(-)
>  delete mode 100644 arch/um/include/shared/aio.h
>  delete mode 100644 arch/um/os-Linux/aio.c

Thanks,

                Linus
Richard Weinberger Oct. 31, 2018, 11:01 p.m. UTC | #2
Am Mittwoch, 31. Oktober 2018, 23:48:07 CET schrieb Linus Torvalds:
> On Wed, Oct 31, 2018 at 2:22 PM Richard Weinberger <richard@nod.at> wrote:
> >
> > - Removal of old and dead code
> > - A bug fix for our tty driver
> > - Other minor cleanups across the code base
> 
> Pulled. I may not like recent rebases, but I do like this:

Okay, so my rebase was in vain, I thought you don't like pull requests
with such an old base.

Thanks,
//richard
Linus Torvalds Oct. 31, 2018, 11:05 p.m. UTC | #3
On Wed, Oct 31, 2018 at 4:01 PM Richard Weinberger <richard@nod.at> wrote:
>
> Okay, so my rebase was in vain, I thought you don't like pull requests
> with such an old base.

Some *really* old bases can cause problems, but generally that's if
it's more than a year old (or if there's been some major upheaval that
happens to particularly strike your particular code).

Honestly, I don't think I can recall any actual "that is based on
something so old that it actually gets problematic" case ever having
happened.  But I could imagine it.

So if it's "a release or two", it's not worth rebasing for. Not unless
there is some other pressing reason (ie some screw-up that requires a
rebase).

                   Linus