From: Takashi Iwai <tiwai@suse.de>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, perex@suse.de
Subject: Re: ALSA update broke Sparc
Date: Wed, 01 Sep 2004 10:14:59 +0200 [thread overview]
Message-ID: <s5hbrgqz9q4.wl@alsa2.suse.de> (raw)
In-Reply-To: <20040831135805.371c5c33.davem@davemloft.net>
At Tue, 31 Aug 2004 13:58:05 -0700,
David S. Miller wrote:
>
>
> Also, please do not use __i386__ et al. ifdefs, use
> things like CONFIG_I386 and CONFIG_SPARC which are
> meant for this purpose.
Do we have CONFIG_I386?
At least, CONFIG_X86 is defined also for x86-64, so it's not unique.
(For my patch it's ok since both are given, though.)
Takashi
next prev parent reply other threads:[~2004-09-01 8:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-28 1:36 ALSA update broke Sparc David S. Miller
2004-08-28 7:45 ` Russell King
2004-08-30 10:26 ` Takashi Iwai
2004-08-31 19:07 ` Takashi Iwai
2004-08-31 20:56 ` David S. Miller
2004-09-01 8:12 ` Takashi Iwai
2004-08-31 20:58 ` David S. Miller
2004-09-01 8:14 ` Takashi Iwai [this message]
2004-08-31 22:20 ` Andrew Morton
2004-09-01 8:16 ` Takashi Iwai
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=s5hbrgqz9q4.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.de \
/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