From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] AVR32 update for 2.6.18-rc2-mm1
Date: Mon, 31 Jul 2006 11:40:58 -0700 [thread overview]
Message-ID: <1154371259.13744.4.camel@localhost> (raw)
In-Reply-To: <20060731174659.72da734f@cad-250-152.norway.atmel.com>
On Mon, 2006-07-31 at 17:46 +0200, Haavard Skinnemoen wrote:
> On Mon, 31 Jul 2006 15:55:15 +0200
> Haavard Skinnemoen <hskinnemoen@atmel.com> wrote:
>
> > Anyway, 2.6.18-rc2-mm1 boots successfully on my target with these
> > patches, but there's something strange going on with NFS and a few
> > other things that I didn't notice on 2.6.18-rc1. I'll investigate
> > some more and see if I can figure out what's going on.
>
> All forms of write access to the NFS root file system seem to return
> -EACCESS. If I leave out git-nfs.patch, the problem goes away, so I'll
> try bisecting the NFS git tree tomorrow.
can you check in /proc/self/mountstats what mount options are set on the
root file system?
> Is there anyway to access it via http?
The individual patches are archived in
http://client.linux-nfs.org/Linux-2.6.x/2.6.18-rc3/
There is also gitweb access via
http://linux-nfs.org/cgi-bin/gitweb.cgi
Cheers,
Trond
next prev parent reply other threads:[~2006-07-31 18:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 13:55 [PATCH 0/6] AVR32 update for 2.6.18-rc2-mm1 Haavard Skinnemoen
2006-07-31 15:46 ` Haavard Skinnemoen
2006-07-31 18:40 ` Trond Myklebust [this message]
2006-08-01 8:12 ` Haavard Skinnemoen
2006-08-01 16:47 ` Trond Myklebust
2006-08-01 17:39 ` David Howells
2006-08-01 18:08 ` Trond Myklebust
2006-08-01 18:22 ` David Howells
2006-08-02 7:45 ` Haavard Skinnemoen
2006-08-03 14:34 ` Trond Myklebust
2006-08-03 15:33 ` Haavard Skinnemoen
2006-08-03 15:46 ` David Howells
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=1154371259.13744.4.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@osdl.org \
--cc=hskinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.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.