From: Al Viro <viro@ZenIV.linux.org.uk>
To: Richard Weinberger <richard@nod.at>
Cc: linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH] um: Cleanup headers files
Date: Sat, 4 Feb 2012 00:14:31 +0000 [thread overview]
Message-ID: <20120204001431.GY23916@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1328311063-17630-1-git-send-email-richard@nod.at>
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
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Richard Weinberger <richard@nod.at>
Cc: user-mode-linux-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] um: Cleanup headers files
Date: Sat, 4 Feb 2012 00:14:31 +0000 [thread overview]
Message-ID: <20120204001431.GY23916@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1328311063-17630-1-git-send-email-richard@nod.at>
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
next prev parent reply other threads:[~2012-02-04 0:14 UTC|newest]
Thread overview: 26+ 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 ` [uml-devel] " Al Viro
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 [this message]
2012-02-04 0:14 ` Al Viro
2012-02-04 0:26 ` Richard Weinberger
2012-02-04 0:44 ` [uml-devel] " Richard Weinberger
2012-02-04 0:44 ` Richard Weinberger
2012-02-12 20:27 ` [uml-devel] " Al Viro
2012-02-12 20:27 ` Al Viro
2012-02-12 21:01 ` [uml-devel] " Richard Weinberger
2012-02-12 21:01 ` Richard Weinberger
2012-02-12 21:20 ` [uml-devel] " Al Viro
2012-02-12 21:20 ` Al Viro
2012-02-12 21:26 ` Richard Weinberger
2012-02-12 21:26 ` Richard Weinberger
2012-02-12 21:28 ` [uml-devel] " Al Viro
2012-02-12 21:28 ` Al Viro
2012-02-04 14:05 ` [uml-devel] " Richard Weinberger
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=20120204001431.GY23916@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.