public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric B Munson <ebmunson@us.ibm.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-rdma@vger.kernel.org, rolandd@cisco.com,
	peterz@infradead.org, pavel@ucw.cz, mingo@elte.hu
Subject: Re: [PATCH] ummunotify: fix umn-test build
Date: Sat, 17 Apr 2010 21:44:05 +0400	[thread overview]
Message-ID: <20100417174404.GB3579@us.ibm.com> (raw)
In-Reply-To: <20100414094341.ba69842d.randy.dunlap@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 325 bytes --]

On Wed, 14 Apr 2010, Randy Dunlap wrote:

> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> Add ummunotify.h to Kbuild list for export to userspace,
> fixing 27 build errors in umn-test.c when O=builddir is used.
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>

Thanks, will wrap this into V2.

Eric

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2010-04-17 17:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12  6:22 [PATCH] ummunotify: Userspace support for MMU notifications Eric B Munson
2010-04-12 20:20 ` Pavel Machek
2010-04-12 23:03 ` Andrew Morton
2010-04-12 23:59   ` Jason Gunthorpe
2010-04-13  8:29     ` Håkon Bugge
2010-04-13 17:57       ` Roland Dreier
2010-04-13 18:02         ` Peter Zijlstra
2010-04-14  5:18           ` Håkon Bugge
2010-04-14  8:52           ` Gleb Natapov
2010-04-15 13:48             ` Peter Zijlstra
2010-04-14  9:06         ` Gleb Natapov
2010-04-14 14:36           ` Jeff Squyres
2010-04-17 17:41   ` Eric B Munson
2010-04-14 16:43 ` [PATCH] ummunotify: fix umn-test build Randy Dunlap
2010-04-17 17:44   ` Eric B Munson [this message]
2010-04-18 14:38     ` Roland Dreier

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=20100417174404.GB3579@us.ibm.com \
    --to=ebmunson@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pavel@ucw.cz \
    --cc=peterz@infradead.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rolandd@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox