> I'd rather do
>
> pgprot_t prot;
>
> #ifdef CONFIG_PPC
> prot =
> #else
> prot = pgprot_noncached(...)
> #endif
> vma->vm_page_prot = prot;
I have changed my patch accordinly. Thank you.
--
Mit freundlichen Grüßen / met vriendelijke groeten / avec regards
Maxim
On Wed, 2008-07-09 at 11:14 +0200, Maxim Shchetynin wrote:
> Am Wed, 09 Jul 2008 18:58:38 +1000
> schrieb Benjamin Herrenschmidt <[EMAIL PROTECTED]>:
>
> > On Tue, 2008-07-01 at 16:59 +0200, Arnd Bergmann wrote:
> > > I wouldn't hold up merging the file system for this problem, but
> > > until it
Am Wed, 09 Jul 2008 18:58:38 +1000
schrieb Benjamin Herrenschmidt <[EMAIL PROTECTED]>:
> On Tue, 2008-07-01 at 16:59 +0200, Arnd Bergmann wrote:
> > I wouldn't hold up merging the file system for this problem, but
> > until it is solved, the Kconfig entry should probably have
> > a "depends on PPC
On Tue, 2008-07-01 at 16:59 +0200, Arnd Bergmann wrote:
> I wouldn't hold up merging the file system for this problem, but
> until it is solved, the Kconfig entry should probably have
> a "depends on PPC".
Better, use an ifdef for powerpc flags, and #else to pgprot_noncached.
Ben.
_
> Cc:'ing some more people that might have more of a clue on this question.
> _memcpy_fromio does a "sync" at the start and an "eieio" at the end.
> IFAICT, neither are needed here because the source is always memory.
>
> It also handles unaligned memory accesses, which copy_to_user should
> also
On Monday 07 July 2008, Maxim Shchetynin wrote:
> > > + if (copy_to_user(target, (void*) pin, size)) {
> > > + rc = -EFAULT;
> > > + goto out;
> > > + }
> >
> > Question to the powerpc folks: is copy_to_user safe for an __iomem source?
> > Sh
Thank you Arnd for your comments. I have changed my patch accordinly (I will
send it in a few minutes).
> > Subject: azfs: initial submit of azfs, a non-buffered filesystem
>
> Please make the patch subject the actual subject of your email next time,
> and put the introductory text below the Sig
On Wednesday 18 June 2008, Maxim Shchetynin wrote:
> AZFS patch updated accordinly to comments of Christoph Hellwig and Dmitri
> Vorobiev.
Sorry for my not commenting earlier on this. I'm finally collecting my
2.6.27 patches and stumbled over it again. There are a few details
that I hope we can f
