From: Rob Landley <rob@landley.net>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] Re: [PATCH 2/4] UML - Eliminate anonymous union and clean up symlink lossage
Date: Fri, 18 Nov 2005 01:10:34 -0600 [thread overview]
Message-ID: <200511180110.35169.rob@landley.net> (raw)
In-Reply-To: <200511180103.29950.rob@landley.net>
On Friday 18 November 2005 01:03, Rob Landley wrote:
> On Thursday 17 November 2005 15:10, Jeff Dike wrote:
> > This gives a name to the anonymous union introduced in
> > skas-hold-own-ldt, allowing to build on a wider range of gccs.
>
> Or narrower range, in the case of Ubuntu "Horny Hedgehog". 2.6.15-rc1
> builds fine by itself, or with just patch 1 in this series, but with patch
> 2...
To clarify, 1, 3 and 4 in this series all build fine for me. Only patch 2 is
breaking my build.
Rob
prev parent reply other threads:[~2005-11-18 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 21:10 [PATCH 2/4] UML - Eliminate anonymous union and clean up symlink lossage Jeff Dike
2005-11-18 7:03 ` Rob Landley
2005-11-18 7:10 ` Rob Landley [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=200511180110.35169.rob@landley.net \
--to=rob@landley.net \
--cc=akpm@osdl.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox