All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Ryan Jackson <rjackson@lnxi.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] [PATCH] [MTD] MAPS: Support for BIOS flash chips on the nvidia ck804 southbridge
Date: Wed, 25 Oct 2006 14:35:03 +0300	[thread overview]
Message-ID: <1161776104.3260.201.camel@sauron> (raw)
In-Reply-To: <20061024174606.GE21009@localdomain>

Hello Ryan,

please, find few of my minor notes below:

> +/*
> + * ck804xrom.c
> + *
> + * Normal mappings of chips in physical memory
> + * $Id: ck804xrom.c,v 1.1 2005/01/06 16:58:24 dolsen Exp $
No need to dubmit CVS stuff
Also it would be nice to add your name at the header.

> + */

> +#include <linux/config.h>
Don't include this file - this stuff is done by the Linux build system. 

> +#define MOD_NAME KBUILD_BASENAME
> +
> +#define ADDRESS_NAME_LEN 18
> +
> +#define ROM_PROBE_STEP_SIZE (64*1024) /* 64KiB */
I personally would be happier to see a comment about what this macro is,
not about that 64*1024 = 64KiB.


> +	/* Free all of the mtd devices */
> +	list_for_each_entry_safe(map, scratch, &window->maps, list) {
> +		if (map->rsrc.parent) {
> +			release_resource(&map->rsrc);
> +		}
{} for one-line operators are not needed as well as all over the code -
that's a linux coding style convention.

> +        pci_write_config_byte(pdev, 0x88, byte | (1<<6));
> +	}
> +	else {
> +		window->phys = 0xffff0000; /* 64KiB */
Please, use } else { instead.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2006-10-25 11:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-24 17:46 [PATCH] [PATCH] [MTD] MAPS: Support for BIOS flash chips on the nvidia ck804 southbridge Ryan Jackson
2006-10-25 11:35 ` Artem Bityutskiy [this message]
2006-10-25 16:43   ` Ryan Jackson
2006-10-25 12:39 ` David Woodhouse
2006-10-25 17:36   ` Ryan Jackson

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=1161776104.3260.201.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rjackson@lnxi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.