All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Borislav Petkov <bp@suse.de>, LKML <linux-kernel@vger.kernel.org>,
	Sasha Levin <sasha.levin@oracle.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	virtio-dev@lists.oasis-open.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] tools: Unify export.h
Date: Tue, 25 Feb 2014 11:05:11 -0300	[thread overview]
Message-ID: <20140225140511.GD5982@ghostprotocols.net> (raw)
In-Reply-To: <87eh2r4c2d.fsf@rustcorp.com.au>

Em Tue, Feb 25, 2014 at 10:52:02PM +1030, Rusty Russell escreveu:
> Borislav Petkov <bp@suse.de> writes:
> > On Tue, Feb 25, 2014 at 12:09:23PM +1030, Rusty Russell wrote:
> >> Should we get more ambitious and start a fake-kernel/ directory where
> >> we can put userspace equivs/stubs of kernel functionality?
> >
> > Dunno - people like to do that now, it seems.
> >
> > In any case, cleanups and unifications like that would definitely help
> > if we decide to do that because, in this particular example, we have
> > only one export.h to go and fish out.
> 
> Agreed.
> 
> Acked-by: Rusty Russell <rusty@rustcorp.com.au>

I'm ok with it as well and will stash it in my perf/core branch after
a bit more time for others in the CC list to say something.

- Arnaldo

  parent reply	other threads:[~2014-02-25 14:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23 11:09 [PATCH] tools: Unify export.h Borislav Petkov
2014-02-25  1:39 ` Rusty Russell
2014-02-25  7:00   ` Borislav Petkov
2014-02-25  7:00   ` Borislav Petkov
2014-02-25 12:22     ` Rusty Russell
2014-02-25 12:22       ` Rusty Russell
2014-02-25 14:05       ` Arnaldo Carvalho de Melo
2014-02-25 14:05       ` Arnaldo Carvalho de Melo [this message]
2014-04-10 17:38         ` Borislav Petkov
2014-04-10 17:38           ` Borislav Petkov
2014-04-11 11:59           ` Jiri Olsa
2014-04-11 11:59           ` Jiri Olsa
2014-04-12 10:14             ` Borislav Petkov
2014-04-12 10:14               ` Borislav Petkov
2014-04-13 11:27               ` [PATCH] tools: Consolidate types.h Borislav Petkov
2014-04-13 11:27                 ` Borislav Petkov
2014-04-14 11:18                 ` Jiri Olsa
2014-04-14 11:18                   ` Jiri Olsa
2014-02-25  1:39 ` [PATCH] tools: Unify export.h Rusty Russell
  -- strict thread matches above, loose matches on Subject: below --
2014-02-23 11:09 Borislav Petkov

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=20140225140511.GD5982@ghostprotocols.net \
    --to=acme@ghostprotocols.net \
    --cc=a.p.zijlstra@chello.nl \
    --cc=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mst@redhat.com \
    --cc=paulus@samba.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sasha.levin@oracle.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtualization@lists.linux-foundation.org \
    /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.