From: Hans Reiser <reiser@namesys.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jeff Mahoney <jeffm@suse.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-bugzilla@luksan.cjb.net
Subject: quality control
Date: Sun, 05 Feb 2006 19:15:20 -0800 [thread overview]
Message-ID: <43E6BF48.5010301@namesys.com> (raw)
In-Reply-To: <43E6521F.5020707@suse.com>
Dearest HCH,
Please consider adhering to a quality control process. No patch comes
out of Namesys without a second person testing it (that includes
compiling it). Users should not be burdened with code that has not been
tested by a second person. Everyone makes mistakes of this kind, the
difference is that some persons use a quality control process to avoid
burdening more than one other person with them.
Hans
Jeff Mahoney wrote:
> Hans Reiser wrote:
>
> >http://bugzilla.kernel.org/show_bug.cgi?id=6016
>
> > Summary: reiserfs doesn't build with REISERFS_FS_POSIX_ACL=n
> > Kernel Version: v2.6.16-rc2-g5b7b644
> > Status: NEW
> > Severity: normal
> > Owner: reiserfs-dev@namesys.com
> > Submitter: kernel-bugzilla@luksan.cjb.net
>
>
> >Most recent kernel where this bug did not occur: 2.6.16-rc1
> >Distribution: Gentoo
> >Hardware Environment: amd64
> >Problem Description:
>
> >reiserfs doesn't build with REISERFS_FS_POSIX_ACL=n
>
> >Steps to reproduce:
> >$ make
> > CHK include/linux/version.h
> > SPLIT include/linux/autoconf.h -> include/config/*
> > CHK include/linux/compile.h
> > CHK usr/initramfs_list
> > GZIP kernel/config_data.gz
> > IKCFG kernel/config_data.h
> > CC kernel/configs.o
> > LD kernel/built-in.o
> > CC fs/reiserfs/xattr.o
> >fs/reiserfs/xattr.c: In function `reiserfs_check_acl':
> >fs/reiserfs/xattr.c:1330: error: called object is not a function
> >make[2]: *** [fs/reiserfs/xattr.o] Error 1
> >make[1]: *** [fs/reiserfs] Error 2
> >make: *** [fs] Error 2
>
> >Reverting ec191574b9c3cb7bfb95e4f803b63f7c8dc52690
> >---
> >[PATCH] reiserfs: use generic_permission
>
> >Use the generic_permission code with a proper wrapper and callback
> instead
> >of having a local copy.
> >---
> >fixes the problem, but causes some warnings about unused symbols.
>
>
> This was a patch from hch, not me. There's already a patch in -mm to
> fix it.
>
> -Jeff
>
> --
> Jeff Mahoney
> SUSE Labs
next parent reply other threads:[~2006-02-06 3:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43E64791.8010302@namesys.com>
[not found] ` <43E6521F.5020707@suse.com>
2006-02-06 3:15 ` Hans Reiser [this message]
2006-02-06 3:39 ` quality control Kyle Moffett
2006-02-06 9:09 ` Jens Axboe
2006-02-06 9:15 ` Martin Mares
2006-02-06 11:09 ` Andi Kleen
2006-02-06 13:31 ` Kyle Moffett
2006-02-06 13:44 ` Jens Axboe
2006-02-07 22:44 ` Andrew Morton
2006-02-08 8:45 ` Jens Axboe
2006-02-06 19:27 ` Olaf Hering
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=43E6BF48.5010301@namesys.com \
--to=reiser@namesys.com \
--cc=hch@infradead.org \
--cc=jeffm@suse.com \
--cc=kernel-bugzilla@luksan.cjb.net \
--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.