linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org,
	linux-ppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] MPC8xx PCMCIA driver
Date: Wed, 14 Sep 2005 16:27:46 +0200	[thread overview]
Message-ID: <20050914142746.GA14742@isilmar.linta.de> (raw)
In-Reply-To: <20050914141131.GA6830@dmt.cnet>

On Wed, Sep 14, 2005 at 11:11:31AM -0300, Marcelo Tosatti wrote:
> On Thu, Sep 01, 2005 at 10:53:19AM +0200, Dominik Brodowski wrote:
> 
> > > +typedef struct  {
> > > +	u_int regbit;
> > > +	u_int eventbit;
> > > +} event_table_t;
> > 
> > No typedefs, please.
> 
> OK, I've converted it to a plain "struct".

Thanks.

> I think this code is just following PCMCIA style:
> 
> typedef struct pccard_mem_map { 
> 	u_char	map;
> 	u_char	flags;
> 	u_short	speed;
> 	u_long	static_start;
> 	u_int	card_start;
> 	struct resource *res;
> } pccard_mem_map;
>
> Any reason why this typedef and similar ones in ss.h 
> are wanted? 

There's no reason for this being typedef'ed, and it is contrary to the
kernel source CodingStyle. However, all pcmcia code was external at first,
that's why the CodingStyle differs.

> PCMCIA is also using u_xxx "weird data types" extensively.

Unfortunately, yes. However, I'm in the process of adapting it to the kernel
CodingStyle. I don't change something from "u_int" to "unsigned int" just for
the naming of it, though, but when I'm in the same area fixing one thing or
another, I try to take care of it. New structs, like struct pcmcia_device, 
already adhere the normal kernel policy on structs and typedefs.

Thanks,
	Dominik

  reply	other threads:[~2005-09-14 14:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30  2:48 [PATCH] MPC8xx PCMCIA driver Marcelo Tosatti
2005-08-30  3:39 ` Jeff Garzik
2005-08-30  3:53   ` Marcelo Tosatti
2005-08-30  4:32     ` Paul Mackerras
2005-08-30 15:07       ` Marcelo Tosatti
2005-08-30  4:33     ` Jeff Garzik
2005-08-30  7:06 ` Russell King
2005-09-01  8:53 ` Dominik Brodowski
2005-09-01 11:44   ` Magnus Damm
2005-09-01 14:51   ` Marcelo Tosatti
2005-09-14 14:11   ` Marcelo Tosatti
2005-09-14 14:27     ` Dominik Brodowski [this message]
2005-09-14 18:21       ` Marcelo Tosatti
2005-09-14 18:46         ` Jeff Garzik

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=20050914142746.GA14742@isilmar.linta.de \
    --to=linux@dominikbrodowski.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=marcelo.tosatti@cyclades.com \
    /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).