linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@mcmartin.ca>
To: Christoph Hellwig <hch@lst.de>
Cc: James Bottomley <James.Bottomley@suse.de>,
	linux-arch@vger.kernel.org, linux-parisc@vger.kernel.org,
	rmk@arm.linux.org.uk, lethal@linux-sh.org,
	torvalds@linux-foundation.org,
	James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCHv3 0/5] fix xfs by making I/O to vmap/vmalloc areas work
Date: Sat, 6 Feb 2010 19:26:38 -0500	[thread overview]
Message-ID: <20100207002638.GQ24051@bombadil.infradead.org> (raw)
In-Reply-To: <20100205160640.GA24344@lst.de>

On Fri, Feb 05, 2010 at 05:06:40PM +0100, Christoph Hellwig wrote:
> > From: James Bottomley <James.Bottomley@HansenPartnership.com>
> > 
> 
> Agreed.  There's also a lot of ARM users popping up with this recently,
> while others worked around it using local flushing hacks previously.
> 

Thanks, I've applied these to parisc/next to give them a shakedown in
linux-next.

regards, Kyle.

  reply	other threads:[~2010-02-07  0:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05 15:50 [PATCHv3 0/5] fix xfs by making I/O to vmap/vmalloc areas work James Bottomley
2010-02-05 15:50 ` [PATCHv3 1/5] mm: add coherence API for DMA to vmalloc/vmap areas James Bottomley
2010-02-05 15:50   ` [PATCHv3 2/5] parisc: add mm " James Bottomley
2010-02-05 15:50     ` James Bottomley
2010-02-05 15:50     ` [PATCHv3 3/5] arm: " James Bottomley
2010-02-05 15:50       ` James Bottomley
2010-02-05 15:50       ` [PATCHv3 4/5] sh: " James Bottomley
2010-02-05 15:50         ` James Bottomley
2010-02-05 15:50         ` [PATCHv3 5/5] xfs: fix xfs to work with Virtually Indexed architectures James Bottomley
2010-02-05 16:06 ` [PATCHv3 0/5] fix xfs by making I/O to vmap/vmalloc areas work Christoph Hellwig
2010-02-07  0:26   ` Kyle McMartin [this message]
2010-02-07  0:26     ` Kyle McMartin

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=20100207002638.GQ24051@bombadil.infradead.org \
    --to=kyle@mcmartin.ca \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=James.Bottomley@suse.de \
    --cc=hch@lst.de \
    --cc=lethal@linux-sh.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=torvalds@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).