All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: "Daniel Aragonés" <danarag@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
	penberg@cs.helsinki.fi, arjan@infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH/RFC] minix filesystem update to V3 diffed to 2.6.17-rc3
Date: Mon, 01 May 2006 19:53:33 +0159	[thread overview]
Message-ID: <44564B34.6020109@gmail.com> (raw)
In-Reply-To: <4456430C.2040806@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Daniel Aragonés napsal(a):
> Hi Andrew,
> 
> Well, I don't know how to solve it. If I don't allocate with kmalloc,
> the compiler stops with error. If I free memory with kfree instead of
> setting offset = NULL, an exception is produced.
Ok, which error?

regards,
- --
Jiri Slaby         www.fi.muni.cz/~xslaby
\_.-^-._   jirislaby@gmail.com   _.-^-._/
B67499670407CE62ACC8 22A032CC55C339D47A7E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFEVks0MsxVwznUen4RAtfpAJ4i+UT6oK2juNxRy1cUH+hJK1JpFACfftk9
6e1qvdAzp9sXduHNKo/5/lI=
=LfQg
-----END PGP SIGNATURE-----

  reply	other threads:[~2006-05-01 17:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-01 13:05 [PATCH/RFC] minix filesystem update to V3 diffed to 2.6.17-rc3 Daniel Aragonés
2006-05-01 13:41 ` Jiri Slaby
2006-05-01 17:03 ` Andrew Morton
2006-05-01 17:19   ` Daniel Aragonés
2006-05-01 17:54     ` Jiri Slaby [this message]
2006-05-01 18:50       ` Daniel Aragonés
2006-05-01 20:30       ` Joshua Hudson
2006-05-06 16:29 ` Al Viro
2006-05-06 16:37   ` Al Viro
2006-05-06 22:04     ` minixfs bitmaps and associated lossage Al Viro
2006-05-06 22:25       ` Matthew Wilcox
2006-05-06 22:26       ` Linus Torvalds
2006-05-06 23:10         ` Al Viro
2006-05-06 23:42           ` Linus Torvalds
2006-05-07  7:37             ` Al Viro
2006-05-07  7:35       ` Pavel Machek

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=44564B34.6020109@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=danarag@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    /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.