public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Barry Naujok <bnaujok@sgi.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>, xfs-dev <xfs-dev@sgi.com>
Subject: Re: [REVIEW] cleanup - remove bhv_vname_t
Date: Tue, 8 Apr 2008 02:38:22 -0400	[thread overview]
Message-ID: <20080408063822.GA21876@infradead.org> (raw)
In-Reply-To: <op.t89zp3j63jf8g2@pc-bnaujok.melbourne.sgi.com>

On Tue, Apr 08, 2008 at 02:50:17PM +1000, Barry Naujok wrote:
> -
> +

What's this?  both lines look empty.

>  	return -dm_send_namesp_event(event, mp ? mp->m_super : NULL,
>  				    ip1->i_vnode, vp1_right,
>  				    ip2 ? ip2->i_vnode : NULL, vp2_right,
> -				    name1, name2,
> +				    (char *)name1, (char *)name2,

please change dm_send_namesp_event to take a const char aswell.

> +static inline struct xfs_name *
> +xfs_dentry_name(
> +	struct xfs_name	*namep,
> +	struct dentry	*dentry)
> +{
> +	namep->name = dentry->d_name.name;
> +	namep->len = dentry->d_name.len;
> +	return namep;
> +}

As mentioned in my comment to the CI series:  shouldn't you just use
a struct qstr instead of adding a new struct xfs_name?

Also please don't add inline for this.
> +xfs_name_t xfs_name_dotdot = {"..", 2};

const?

> +	args.name = name->name;
> +	args.namelen = name->len;
> +	args.hashval = xfs_da_hashname(name->name, name->len);

What about just putting a pointer to the xfs_name/qstr into args?

>  /*
> + * Counted string for file names.
> + */
> +typedef struct xfs_name {
> +	const uchar_t	*name;
> +	int		len;
> +} xfs_name_t;

Please try to avoid the typedef for newly added types.

  parent reply	other threads:[~2008-04-08  6:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-08  4:50 [REVIEW] cleanup - remove bhv_vname_t Barry Naujok
2008-04-08  5:13 ` David Chinner
2008-04-08  6:38 ` Christoph Hellwig [this message]
2008-04-08  6:50   ` Barry Naujok
2008-04-08  7:41     ` Christoph Hellwig
2008-04-08  7:48       ` Barry Naujok

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=20080408063822.GA21876@infradead.org \
    --to=hch@infradead.org \
    --cc=bnaujok@sgi.com \
    --cc=xfs-dev@sgi.com \
    --cc=xfs@oss.sgi.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