From: Linus Torvalds <torvalds@linux-foundation.org>
To: richard@nod.at
Cc: linux-um@lists.infradead.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] UML changes for 4.20-rc1
Date: Wed, 31 Oct 2018 15:48:07 -0700 [thread overview]
Message-ID: <CAHk-=wjw8qra+SYDDjvSnZ=APsn9aFG9WiJGSLD94A0Q_+BZWg@mail.gmail.com> (raw)
In-Reply-To: <1829585.6m1bt7BjAO@blindfold>
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
next prev parent reply other threads:[~2018-10-31 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 21:22 [GIT PULL] UML changes for 4.20-rc1 Richard Weinberger
2018-10-31 22:48 ` Linus Torvalds [this message]
2018-10-31 23:01 ` Richard Weinberger
2018-10-31 23:05 ` 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='CAHk-=wjw8qra+SYDDjvSnZ=APsn9aFG9WiJGSLD94A0Q_+BZWg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
/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).