public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Andrea Arcangeli <andrea@suse.de>
Cc: "J.A. Magallon" <jamagallon@able.es>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.20pre10aa1
Date: Sat, 12 Oct 2002 02:36:42 +0200	[thread overview]
Message-ID: <20021012003642.GG2704@werewolf.able.es> (raw)
In-Reply-To: <20021011232539.GR24468@dualathlon.random>; from andrea@suse.de on Sat, Oct 12, 2002 at 01:25:39 +0200


On 2002.10.12 Andrea Arcangeli wrote:
[...]
>> >
>> >why would you want to remove the list_t declaration? I don't see it.
>> >list_t is just like task_t for struct task_struct etc...
>> >
>> 
>> [..] The main
>> argument was that you can't pre-declare a task_t, but you can
>> with a struct task_t.
>
>so you want to remove task_t too? If yes just grep -v typedef all over
>the tree, and at least it'll be a somehow more coherent decsion ;).
>It's not that list_t forbids you to use struct list_head for
>predeclarations.
>

There is something I do not understand:

struct tst {
	struct x_t	*x;
}

does not need any predeclaraion, tested with gcc -Wall, 2.96, 3.0.4, 3.2.

struct tst {
	x_t	*x;
}

needs it, but you can predeclare a

typedef struct x_t x_t;

if do not want the full include. So I really do not know why everybody
agreed on removing it.

???

-- 
J.A. Magallon <jamagallon@able.es>      \                 Software is like sex:
werewolf.able.es                         \           It's better when it's free
Mandrake Linux release 9.1 (Cooker) for i586
Linux 2.4.20-pre10-jam1 (gcc 3.2 (Mandrake Linux 9.0 3.2-2mdk))

  parent reply	other threads:[~2002-10-12  0:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10 23:09 2.4.20pre10aa1 Andrea Arcangeli
2002-10-11  2:51 ` 2.4.20pre10aa1- build problems Eyal Lebedinsky
     [not found] ` <20021011222830.GA1645@werewolf.able.es>
     [not found]   ` <20021011224237.GQ24468@dualathlon.random>
     [not found]     ` <20021011225228.GE1645@werewolf.able.es>
     [not found]       ` <20021011232539.GR24468@dualathlon.random>
2002-10-12  0:36         ` J.A. Magallon [this message]
2002-10-12  0:43           ` 2.4.20pre10aa1 J.A. Magallon
     [not found]             ` <20021012004827.GA34193@compsoc.man.ac.uk>
2002-10-12  1:04               ` 2.4.20pre10aa1 J.A. Magallon

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=20021012003642.GG2704@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=andrea@suse.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