From: Rasmus Rohde <rohde@duff.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: [NFS] [PATCH] Make UDF exportable
Date: Thu, 07 Feb 2008 08:06:37 +0100 [thread overview]
Message-ID: <1202367997.17388.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20080207054515.GA14585@infradead.org>
Ok - I have checked get_parent and it works as expected.
I used the "Neil Brown"-test mentioned elsewhere in this thread and
added a few printk's to make sure we actually got the code covered.
> There's still a few trivial warnings from scripts/checkpatch.pl that
> should be fixed up:
Fixed that. Sorry for not running checkpatch.pl before submitting.
Before posting the last and hopefully final patch I'd like to know what
Jan says about open coding the lookup for ..
It will mean a lot of code duplication and I think it makes good sense
for udf_find_entry to be able to handle ..
next prev parent reply other threads:[~2008-02-07 7:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1201726404.2976.8.camel@localhost.localdomain>
2008-02-05 10:29 ` [NFS] [PATCH] Make UDF exportable Christoph Hellwig
2008-02-05 17:44 ` Rasmus Rohde
2008-02-05 19:26 ` Rasmus Rohde
2008-02-06 18:08 ` Jan Kara
2008-02-06 20:58 ` Rasmus Rohde
2008-02-07 3:37 ` Christoph Hellwig
2008-02-07 3:44 ` Neil Brown
2008-02-07 5:45 ` Christoph Hellwig
2008-02-07 7:06 ` Rasmus Rohde [this message]
2008-02-07 14:48 ` Jan Kara
[not found] ` <20080207144859.GJ6140-pwKtmJkCtMINMLpHRKhSow@public.gmane.org>
2008-02-07 15:02 ` Rasmus Rohde
2008-02-07 15:13 ` Jan Kara
2008-04-29 14:33 ` Christoph Hellwig
2008-04-30 15:41 ` Jan Kara
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=1202367997.17388.6.camel@localhost.localdomain \
--to=rohde@duff.dk \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/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