linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruen@suse.de>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	ext2-devel@lists.sourceforge.net, tytso@mit.edu,
	Matt Reppert <arashi@arashi.yi.org>
Subject: Re: [Ext2-devel] [PATCH] Compile without xattrs
Date: Tue, 15 Oct 2002 12:11:19 +0200	[thread overview]
Message-ID: <200210151211.19353.agruen@suse.de> (raw)
In-Reply-To: <20021015005733.3bbde222.arashi@arashi.yi.org>

On Tuesday 15 October 2002 07:57, Matt Reppert wrote:
> On Mon, 14 Oct 2002 22:10:41 -0700
>
> Andrew Morton <akpm@digeo.com> wrote:
> > - merge up the ext2/3 extended attribute code, convert that to use
> >   the slab shrinking API in Linus's current tree.
>
> Trivial patch for the "too chicken to enable xattrs for now" case, but I
> need this to compile:

Please add this to include/linux/errno.h instead:

#define ENOTSUP EOPNOTSUPP      /* Operation not supported */

ENOTSUPP is distinct from (EOPNOTSUPP = ENOTSUP)

(Yes, it's a mess.)

--Andreas.

> --- linux-2.5-orig/include/linux/ext2_xattr.h	2002-10-15 00:47:03 -0500
> +++ linux-2.5/include/linux/ext2_xattr.h	2002-10-15 00:45:48 -0500
> @@ -92,20 +92,20 @@
>  ext2_xattr_get(struct inode *inode, int name_index,
>  	       const char *name, void *buffer, size_t size)
>  {
> -	return -ENOTSUP;
> +	return -ENOTSUPP;
>  }
>
>  static inline int
>  ext2_xattr_list(struct inode *inode, char *buffer, size_t size)
>  {
> -	return -ENOTSUP;
> +	return -ENOTSUPP;
>  }
>
>  static inline int
>  ext2_xattr_set(struct inode *inode, int name_index, const char *name,
>  	       const void *value, size_t size, int flags)
>  {
> -	return -ENOTSUP;
> +	return -ENOTSUPP;
>  }
>
>  static inline void
> --- linux-2.5-orig/include/linux/ext3_xattr.h	2002-10-15 00:49:59.000000000
> -0500 +++ linux-2.5/include/linux/ext3_xattr.h	2002-10-15
> 00:50:12.000000000 -0500 @@ -92,20 +92,20 @@
>  ext3_xattr_get(struct inode *inode, int name_index, const char *name,
>  	       void *buffer, size_t size, int flags)
>  {
> -	return -ENOTSUP;
> +	return -ENOTSUPP;
>  }
>
>  static inline int
>  ext3_xattr_list(struct inode *inode, void *buffer, size_t size, int flags)
>  {
> -	return -ENOTSUP;
> +	return -ENOTSUPP;
>  }
>
>  static inline int
>  ext3_xattr_set(handle_t *handle, struct inode *inode, int name_index,
>  	       const char *name, const void *value, size_t size, int flags)
>  {
> -	return -ENOTSUP;
> +	return -ENOTSUPP;
>  }
>
>  static inline void
>
>
> Matt

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  parent reply	other threads:[~2002-10-15 10:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15  5:10 2.5.43-m3 Andrew Morton
2002-10-15  5:20 ` 2.5.43-m3 Andrew Morton
2002-10-15  5:57 ` [PATCH] Compile without xattrs Matt Reppert
2002-10-15  6:05   ` Andrew Morton
2002-10-15 10:11   ` Andreas Gruenbacher [this message]
2002-10-15 10:54     ` [Ext2-devel] " Christoph Hellwig
2002-10-15 11:18     ` Theodore Ts'o

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=200210151211.19353.agruen@suse.de \
    --to=agruen@suse.de \
    --cc=akpm@digeo.com \
    --cc=arashi@arashi.yi.org \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tytso@mit.edu \
    /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