From: Richard Weinberger <richard@nod.at>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: user-mode-linux-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] um: Cleanup headers files
Date: Sat, 04 Feb 2012 01:44:42 +0100 [thread overview]
Message-ID: <4F2C7F7A.1090605@nod.at> (raw)
In-Reply-To: <20120204001431.GY23916@ZenIV.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
Am 04.02.2012 01:14, schrieb Al Viro:
> On Sat, Feb 04, 2012 at 12:17:43AM +0100, Richard Weinberger wrote:
>> Many header files can be replaced by generic variants.
>
> Umm... I suspect that for auxvec.h the right thing is to simply
> remove it - it's never used on uml builds.
>
> FWIW, I've rebased my local queue to current and pushed it to kernel.org
> again; it's on git.kernel.org/pub/scm/linux/kernel/git/viro/um-headers.git
So, I pulled your work and merged it into my shiny new UML tree:
git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git
Thanks,
//richard
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2012-02-04 0:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 17:23 [PATCH 1/2] um: Use generic io.h Richard Weinberger
2012-01-25 17:23 ` [PATCH 2/2] um: Serve io_remap_pfn_range() Richard Weinberger
2012-01-30 18:23 ` [PATCH 1/2] um: Use generic io.h Al Viro
2012-01-30 19:10 ` Richard Weinberger
2012-01-30 19:25 ` Al Viro
2012-01-30 19:32 ` Al Viro
2012-01-30 19:57 ` Richard Weinberger
2012-02-03 23:17 ` [PATCH] um: Cleanup headers files Richard Weinberger
2012-02-04 0:14 ` Al Viro
2012-02-04 0:26 ` Richard Weinberger
2012-02-04 0:44 ` Richard Weinberger [this message]
2012-02-12 20:27 ` Al Viro
2012-02-12 21:01 ` Richard Weinberger
2012-02-12 21:20 ` Al Viro
2012-02-12 21:26 ` Richard Weinberger
2012-02-12 21:28 ` Al Viro
2012-02-04 14:05 ` Richard Weinberger
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=4F2C7F7A.1090605@nod.at \
--to=richard@nod.at \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=viro@ZenIV.linux.org.uk \
/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).