public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: Takashi Iwai <tiwai@suse.de>, Carlos Munoz <carlos@kenati.com>,
	Adrian McMenamin <adrian@mcmen.demon.co.uk>,
	Alsa-devel <alsa-devel@lists.sourceforge.net>,
	linux-sh <linuxsh-dev@lists.sourceforge.net>,
	Paul Mundt <lethal@linux-sh.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Alsa-devel] Re: Patch for AICA sound support on SEGA Dreamcast
Date: Mon, 03 Apr 2006 20:36:25 -0400	[thread overview]
Message-ID: <1144110986.22082.4.camel@mindpipe> (raw)
In-Reply-To: <200604040116.13732.s0348365@sms.ed.ac.uk>

On Tue, 2006-04-04 at 01:16 +0100, Alistair John Strachan wrote:
> I think this write-up provides justification. However, it is not part
> of linux/Documentation/CodingStyle. Perhaps somebody should add these
> details to this file, so that new code follows this currently
> 'unwritten' rule. 

Well, if you look at the current ALSA code, the only typedefs provided
are for backwards compatibility.  They were all removed from the drivers
months ago.  The problem is that you were working against old code.  The
main coding style rule is to follow the conventions of the nearby code,
which would mean no typedefs in the ALSA driver case.

Lee


  reply	other threads:[~2006-04-04  0:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1144075522.11511.20.camel@localhost.localdomain>
2006-04-03 15:52 ` Patch for AICA sound support on SEGA Dreamcast Takashi Iwai
2006-04-03 17:48   ` Adrian McMenamin
2006-04-03 18:29     ` Takashi Iwai
2006-04-03 22:36       ` [Alsa-devel] " Adrian McMenamin
2006-04-03 18:00   ` Carlos Munoz
2006-04-03 18:32     ` Takashi Iwai
2006-04-04  0:16       ` Alistair John Strachan
2006-04-04  0:36         ` Lee Revell [this message]
2006-04-15 19:34   ` [Alsa-devel] " Adrian McMenamin

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=1144110986.22082.4.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=adrian@mcmen.demon.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=carlos@kenati.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxsh-dev@lists.sourceforge.net \
    --cc=s0348365@sms.ed.ac.uk \
    --cc=tiwai@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