All of lore.kernel.org
 help / color / mirror / Atom feed
From: Radu Moisan <radu.moisan@intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] udev: enable multilib support
Date: Thu, 04 Apr 2013 11:48:15 +0300	[thread overview]
Message-ID: <515D3E4F.3050900@intel.com> (raw)
In-Reply-To: <CAJTo0LbiXC_qKszpNNy5crnpXeGx99Ff9vGzpcXNk4otXgp8GQ@mail.gmail.com>

On 04/03/2013 09:02 PM, Burton, Ross wrote:
> On 3 April 2013 18:58, Koen Kooi <koen@dominion.thruhere.net> wrote:
>> NACK! The udev maintainers have been clear that it is always /lib/udev, even on 64 bit systems, so you're not fixing a problem, you're creating an extra one.
> Radu, can you do a multilib udev build and see what continues to fall
> into /lib64, so we can fix it?  (and the same with systemd)

I'll take a look into this, of course.

Radu



  parent reply	other threads:[~2013-04-04  9:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03 16:25 [PATCH 0/2 v2] Udev multilib fixes Radu Moisan
2013-04-03 16:25 ` [PATCH 1/2] initramfs-live-boot: enable multilib support Radu Moisan
2013-04-03 16:25 ` [PATCH 2/2] udev: " Radu Moisan
2013-04-03 17:58   ` Koen Kooi
2013-04-03 18:02     ` Burton, Ross
2013-04-03 18:05       ` Khem Raj
2013-04-04  8:48       ` Radu Moisan [this message]
2013-04-04 12:45     ` Radu Moisan
2013-04-04 13:03       ` Koen Kooi
2013-04-05 11:59         ` Radu Moisan
2013-04-05 13:29           ` Alex Damian
2013-04-05 14:34             ` Richard Purdie
2013-04-06 10:32               ` Koen Kooi
2013-04-06 22:00                 ` Richard Purdie
2013-04-07  7:54                   ` Koen Kooi
  -- strict thread matches above, loose matches on Subject: below --
2013-04-03 15:51 [PATCH 0/2] Udev multilib fixes Radu Moisan
2013-04-03 15:51 ` [PATCH 2/2] udev: enable multilib support Radu Moisan

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=515D3E4F.3050900@intel.com \
    --to=radu.moisan@intel.com \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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.