linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Domen Puncer <domen@coderock.org>
To: Jan Kara <jack@suse.cz>
Cc: linux-kernel@vger.kernel.org, janitor@sternwelten.at
Subject: Re: [patch 1/1] list_for_each_entry: fs-dquot.c
Date: Tue, 11 Jan 2005 16:32:29 +0100	[thread overview]
Message-ID: <20050111153229.GG4978@nd47.coderock.org> (raw)
In-Reply-To: <20050111143414.GF15061@atrey.karlin.mff.cuni.cz>

On 11/01/05 15:34 +0100, Jan Kara wrote:
>   Hello,
> 
> > Make code more readable with list_for_each_entry_safe.
> > (Didn't compile before, doesn't compile now)
>   What do you mean by "didn't compile before"? Which kernel have you
> tried?

It seems like it was compile tested with quotas disabled.
It compiles fine when i enable quotas, duh.
Sorry.


	Domen

  reply	other threads:[~2005-01-11 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-10 18:42 [patch 1/1] list_for_each_entry: fs-dquot.c domen
2005-01-11 14:34 ` Jan Kara
2005-01-11 15:32   ` Domen Puncer [this message]
2005-06-20 21:56 domen
2005-06-23  8:44 ` Jan Kara

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=20050111153229.GG4978@nd47.coderock.org \
    --to=domen@coderock.org \
    --cc=jack@suse.cz \
    --cc=janitor@sternwelten.at \
    --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;
as well as URLs for NNTP newsgroup(s).