mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Svetoslav Slavtchev" <svetljo@gmx.de>
To: "lkml " <linux-kernel@vger.kernel.org>
Subject: new reiser4 snapshot is available
Date: Fri, 14 Nov 2003 11:43:35 +0100 (MET)	[thread overview]
Message-ID: <26442.1068806615@www67.gmx.net> (raw)

Hi,

1.)--------------------------------------------------
is this done on purpose ?

  CC [M]  fs/reiser4/blocknrset.o
  CC [M]  fs/reiser4/super.o
fs/reiser4/super.c: In function `statfs_type':
fs/reiser4/super.c:41: warning: integer overflow in expression
  CC [M]  fs/reiser4/oid.o
  CC [M]  fs/reiser4/tree_walk.o

gcc version 3.3.1 (Mandrake Linux 9.2 3.3.1-2mdk)

const __u32 REISER4_SUPER_MAGIC = 0x52345362;   /* (*(__u32 *)"R4Sb"); */

static __u64 reserved_for_gid(const struct super_block *super, gid_t gid);
static __u64 reserved_for_uid(const struct super_block *super, uid_t uid);
static __u64 reserved_for_root(const struct super_block *super);

/* Return reiser4-specific part of super block */
reiser4_super_info_data *
get_super_private_nocheck(const struct super_block *super       /* super
block
                                                                 * queried
*/ )
{
        return (reiser4_super_info_data *) super->s_fs_info;
}


/* Return reiser4 fstype: value that is returned in ->f_type field by
statfs() */
long
statfs_type(const struct super_block *super UNUSED_ARG  /* super block
                                                         * queried */ )
{
        assert("nikita-448", super != NULL);
        assert("nikita-449", is_reiser4_super(super));
        return (long) REISER4_SUPER_MAGIC;

2.)--------------------------------------------------------
 CC [M]  fs/jbd/transaction.o
fs/jbd/transaction.c: In function `journal_start':
fs/jbd/transaction.c:283: error: structure has no member named
`journal_info'
fs/jbd/transaction.c:288: error: structure has no member named
`journal_info'
fs/jbd/transaction.c: In function `journal_stop':
fs/jbd/transaction.c:1363: error: structure has no member named
`journal_info'
make[2]: *** [fs/jbd/transaction.o] Error 1
make[1]: *** [fs/jbd] Error 2
make: *** [fs] Error 2

3.)---------------------------------------------------
could you please split the patch ?
may be also drop *.orig :-)
but more importantly drop/splut the uml changes

best,

svetljo

PS.

please CC me as i'm not subscribed

-- 
NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien...
Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService

Jetzt kostenlos anmelden unter http://www.gmx.net

+++ GMX - die erste Adresse für Mail, Message, More! +++


             reply	other threads:[~2003-11-14 10:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-14 10:43 Svetoslav Slavtchev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-14 11:22 Svetoslav Slavtchev
     [not found] <20031113143438.GD1278@backtop.namesys.com>
2003-11-14  9:42 ` Alex Zarochentsev
2003-11-14 11:04   ` Gianni Tedesco
2003-11-14 11:20     ` Alex Zarochentsev
2003-11-14 13:16       ` Alex Zarochentsev
2003-11-14 13:27         ` Carl-Daniel Hailfinger
2003-11-14 13:32           ` Alex Zarochentsev

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=26442.1068806615@www67.gmx.net \
    --to=svetljo@gmx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®