public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: akepner@sgi.com
To: Roland Dreier <rdreier@cisco.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Tony Luck <tony.luck@intel.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Jes Sorensen <jes@sgi.com>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	David Miller <davem@davemloft.net>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Grant Grundler <grundler@parisc-linux.org>,
	Michael Ellerman <michael@ellerman.id.au>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3 v6] IB: expand ib_umem_get() prototype
Date: Tue, 8 Apr 2008 14:29:12 -0700	[thread overview]
Message-ID: <20080408212912.GI29410@sgi.com> (raw)
In-Reply-To: <adar6dgm8yi.fsf@cisco.com>

On Tue, Apr 08, 2008 at 12:40:21PM -0700, Roland Dreier wrote:
> All of this looks good to me, and I'm happy we are finally fixing this
> up.  However, now that it is finally ready to merge, I started thinking
> about the libmthca changes required to handle this, and I realized that
> we can actually avoid this:
> .....
> with my proposed change, the only difference is:
> 
>  new kernel, old userspace: current behavior (subtle failure on Altix),
>                             plus print a warning telling people to
>                             update userspace.
> ....
> 
> Andrew: if Arthur agrees with this, please roll the patch below into the
> current IB patch you have as part of the dma attrs series.

Sounds fine to me, Roland. 

Acked-by: Arthur Kepner <akepner@sgi.com>

-- 
Arthur


      reply	other threads:[~2008-04-08 21:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01  1:37 [PATCH 3/3 v6] IB: expand ib_umem_get() prototype akepner
2008-04-08 19:40 ` Roland Dreier
2008-04-08 21:29   ` akepner [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=20080408212912.GI29410@sgi.com \
    --to=akepner@sgi.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=grundler@parisc-linux.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jes@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@ellerman.id.au \
    --cc=randy.dunlap@oracle.com \
    --cc=rdreier@cisco.com \
    --cc=tony.luck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox