All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 1/9] Use xfs.h rather than libxfs.h
Date: Thu, 28 May 2009 05:56:57 -0400	[thread overview]
Message-ID: <20090528095657.GA651@infradead.org> (raw)
In-Reply-To: <1243450413-12681-2-git-send-email-sandeen@sandeen.net>

On Wed, May 27, 2009 at 01:53:25PM -0500, Eric Sandeen wrote:
> Use xfs/xfs.h when possible rather than xfs/libxfs.h,
> now that libxfs.h isn't part of a normal xfsprogs-devel
> install.

> +/*
> + * MAXNAMELEN is the length (including the terminating null) of
> + * the longest permissible file (component) name.
> + */
> +#ifndef MAXNAMELEN
> +#define MAXNAMELEN 256
> +#endif

Just switch all users to the posix NAME_MAX instead.  Note that NAME_MAX
does not include the NULL termination, so it's one-off vs MAXNAMELEN.

> diff --git a/src/godown.c b/src/godown.c
> index 4105aee..fa04f24 100644
> --- a/src/godown.c
> +++ b/src/godown.c
> @@ -18,7 +18,7 @@
>  
>  #include "global.h"
>  
> -/* These should be in libxfs.h */
> +/* These should be in xfs.h */
>  #ifndef XFS_IOC_GOINGDOWN
>  #define XFS_IOC_GOINGDOWN           _IOR ('X', 125, __uint32_t)
>  #endif

Might be worth to remove now as we had it in xfs_fs.h forever.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-05-28  9:56 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 18:53 [PATCH 0/9] xfstests: more generic fs work Eric Sandeen
2009-05-27 18:53 ` [PATCH 1/9] Use xfs.h rather than libxfs.h Eric Sandeen
2009-05-28  9:56   ` Christoph Hellwig [this message]
2009-05-28 15:46     ` [PATCH 0.5/9] Replace MAXNAMELEN with NAME_MAX + 1 Eric Sandeen
2009-05-28 15:48       ` Christoph Hellwig
2009-05-28 16:16     ` [PATCH 1/9 V2] Use xfs.h rather than libxfs.h Eric Sandeen
2009-05-28 16:22       ` Christoph Hellwig
2009-05-27 18:53 ` [PATCH 2/9] Make libxfs.h optional Eric Sandeen
2009-05-28  9:57   ` Christoph Hellwig
2009-05-28 14:59     ` Eric Sandeen
2009-05-28 15:35       ` Christoph Hellwig
2009-05-28 16:15         ` Eric Sandeen
2009-05-27 18:53 ` [PATCH 3/9] Support "generic" filesystem type Eric Sandeen
2009-05-28  9:58   ` Christoph Hellwig
2009-05-27 18:53 ` [PATCH 4/9] 069: make scratch mkfs quiet Eric Sandeen
2009-05-28  9:58   ` Christoph Hellwig
2009-05-27 18:53 ` [PATCH 5/9] Set up testdir for generic filesystems Eric Sandeen
2009-05-28  9:59   ` Christoph Hellwig
2009-05-27 18:53 ` [PATCH 6/9] Detect FS type to test based on TEST_DEV Eric Sandeen
2009-05-28  9:59   ` Christoph Hellwig
2009-05-27 18:53 ` [PATCH 7/9] Set default extN mount options Eric Sandeen
2009-05-28  9:11   ` Michael Monnerie
2009-05-28 10:02     ` Christoph Hellwig
2009-05-28 10:35       ` Michael Monnerie
2009-05-28 14:56         ` Eric Sandeen
2009-05-29  6:37           ` Michael Monnerie
2009-05-28 10:01   ` Christoph Hellwig
2009-05-28 14:57     ` Eric Sandeen
2009-05-27 18:53 ` [PATCH 8/9] Enable generic filesystems to be fsck'd Eric Sandeen
2009-05-28 12:51   ` Christoph Hellwig
2009-06-02 12:38     ` Christoph Hellwig
2009-06-02 15:10       ` Eric Sandeen
2009-06-02 17:25         ` Christoph Hellwig
2009-05-27 18:53 ` [PATCH 9/9] Report which tests did get run Eric Sandeen
2009-05-28 12:51   ` Christoph Hellwig

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=20090528095657.GA651@infradead.org \
    --to=hch@infradead.org \
    --cc=sandeen@sandeen.net \
    --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 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.