From: David Howells <dhowells@redhat.com>
To: torvalds@linux-foundation.org
Cc: dhowells@redhat.com, arnd@arndb.de, alan@lxorguk.ukuu.org.uk,
hpa@zytor.com, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, airlied@redhat.com
Subject: Pulling the rest of the User-API header split patches
Date: Mon, 16 Jan 2012 15:50:02 +0000 [thread overview]
Message-ID: <10234.1326729002@redhat.com> (raw)
In-Reply-To: <19981.1325887323@redhat.com>
Hi Linus,
Thanks for pulling the User-API header split preliminary patches.
Will you be pulling the rest of the patches to actually perform the split at
the end of this merge window? If so, as previously mentioned, I'll need to
regenerate them before you do.
However, for the moment, I dropped the preliminary patches from my tree and
regenerated the rest based on the tree I saw this morning:
http://git.infradead.org/users/dhowells/linux-headers.git/shortlog/refs/heads/uapi-split
I've made 'make allyesconfig' build again on x86_64. arch/x86/lib/insn.c is
compiled for use in both userspace and kernelspace, necessitating a bit of
#include adjustment, but that was the only necessary change. I've also had
Dave Airlie review the preparatory DRM patches and those have been adjusted.
An opinion, if I may: I have been checking the scripts into the GIT tree (with
the intention to delete them later) so that a record of them is retained - but
I wonder if I should bother... Hopefully, once the scripts are run and the
results applied, it won't be necessary to retain the scripts.
Thanks,
David
prev parent reply other threads:[~2012-01-16 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 22:02 [GIT PULL] User-API header split preliminary patches David Howells
2012-01-16 15:50 ` David Howells [this message]
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=10234.1326729002@redhat.com \
--to=dhowells@redhat.com \
--cc=airlied@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).