linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Grant Erickson <gerickson@nuovations.com>
Cc: linuxppc-dev@ozlabs.org, sr@denx.de
Subject: Re: [PATCH v3] ibm_newemac: Parameterize EMAC Multicast Match Handling
Date: Sun, 06 Jul 2008 08:45:09 +1000	[thread overview]
Message-ID: <1215297909.8970.22.camel@pasglop> (raw)
In-Reply-To: <1215249512-1974-1-git-send-email-gerickson@nuovations.com>

On Sat, 2008-07-05 at 02:18 -0700, Grant Erickson wrote:
> --- a/drivers/net/ibm_newemac/emac.h
> +++ b/drivers/net/ibm_newemac/emac.h
> @@ -41,14 +41,7 @@ struct emac_regs {
>         u32 vtpid;              /* Reset, R, T  */
>         u32 vtci;               /* Reset, R, T  */
>         u32 ptr;                /* Reset,    T  */
> -       u32 iaht1;              /* Reset, R     */
> -       u32 iaht2;              /* Reset, R     */
> -       u32 iaht3;              /* Reset, R     */
> -       u32 iaht4;              /* Reset, R     */
> -       u32 gaht1;              /* Reset, R     */
> -       u32 gaht2;              /* Reset, R     */
> -       u32 gaht3;              /* Reset, R     */
> -       u32 gaht4;              /* Reset, R     */
> +       u32 reserved[8];/* Chip-dependent */
>         u32 lsah;
>         u32 lsal;
>         u32 ipgvr;              /* Reset,    T  */

Mostly looks good. I don't like "reserved" here tho...

Are lsah, lsal and ipgvr still meaningful here ?

If not, just remove everything past "ptr"...

Another option would have been to have emac regs be something
like

struct emac_regs {
	all the common regs
	.../...
	union (
		struct emac4_add_regs {
			emac4 additional regs
		};
		struct emac4sync_add_regs {
			emac4sync additional regs
		}
	};
};

Ben.

  reply	other threads:[~2008-07-05 22:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25  0:08 [PATCH v2] Parameterize EMAC Multicast Match Handling Grant Erickson
2008-07-01  5:26 ` Grant Erickson
2008-07-01  6:14   ` Benjamin Herrenschmidt
2008-07-01  6:37     ` Stefan Roese
2008-07-01 18:13       ` Grant Erickson
2008-07-01 19:42         ` Stefan Roese
2008-07-01 23:52         ` Benjamin Herrenschmidt
2008-07-05  9:18   ` [PATCH v3] ibm_newemac: " Grant Erickson
2008-07-05 22:45     ` Benjamin Herrenschmidt [this message]
2008-07-06  0:15     ` [PATCH v4] " Grant Erickson
2008-07-06  0:31       ` Benjamin Herrenschmidt
2008-07-06  9:43       ` Stefan Roese
2008-07-06 23:30       ` [PATCH v5] " Grant Erickson
2008-07-07  5:58         ` Stefan Roese
2008-07-07  6:00           ` Benjamin Herrenschmidt
2008-07-07  6:29             ` Stefan Roese
2008-07-07  6:43               ` Benjamin Herrenschmidt
2008-07-07  6:18         ` Benjamin Herrenschmidt
2008-07-07 13:59           ` Jeff Garzik
2008-07-07 19:50         ` Valentine Barshak
2008-07-07 22:02           ` Grant Erickson
2008-07-07 22:03         ` [PATCH v6] " Grant Erickson

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=1215297909.8970.22.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=gerickson@nuovations.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sr@denx.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;
as well as URLs for NNTP newsgroup(s).