public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>, Andi Kleen <ak@linux.intel.com>,
	linux-kernel@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH] uml: Fix build with recent glibc
Date: Fri, 02 Mar 2018 09:39:48 +0100	[thread overview]
Message-ID: <2427974.ifqE8EITFz@blindfold> (raw)
In-Reply-To: <20180301183023.00002ddf@intel.com>

Am Freitag, 2. März 2018, 03:30:23 CET schrieb Jesse Brandeburg:
> On Wed, 28 Feb 2018 19:08:44 -0800
> 
> Andi Kleen <andi@firstfloor.org> wrote:
> > From: Andi Kleen <ak@linux.intel.com>
> > 
> > Newer glibc did some include namespace "cleanups" and removed
> > struct ucontext and friends. This already broke a lot of software,
> > and UML seems to be the latest victim.
> > 
> > Use the typedefs which are still available. They also work on
> > older glibcs.
> > 
> > Signed-off-by: Andi Kleen <ak@linux.intel.com>
> 
> same patch that I sent on Feb 1st.  Hope you can get more traction than
> I did.
> 
> https://www.mail-archive.com/user-mode-linux-devel@lists.sourceforge.net/msg
> 10071.html
> 
> Reviewed-by: Jesse Brandeburg <jesse.brandeburg@intel.com>

Sorry guys, due to various reasons in the last months I had not much time for 
UML. But things get better now.
The fix from the first sender is in -next and will hit Linus' tree soon.

Thanks,
//richard

      reply	other threads:[~2018-03-02  8:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01  3:08 [PATCH] uml: Fix build with recent glibc Andi Kleen
2018-03-02  2:30 ` [uml-devel] " Jesse Brandeburg
2018-03-02  8:39   ` Richard Weinberger [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=2427974.ifqE8EITFz@blindfold \
    --to=richard@nod.at \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=jesse.brandeburg@intel.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