netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: "Amit S. Kale" <amitkale@netxen.com>
Cc: netdev@vger.kernel.org, amitkale@netxen.com,
	brazilnut@us.ibm.com, jeff@garzik.org, netxenproj@linsyssoft.com,
	rob@netxen.com, romieu@fr.zoreil.com, sanjeev@netxen.com,
	wendyx@us.ibm.com
Subject: Re: [PATCH 2/3] NetXen: 64-bit memory fixes
Date: Fri, 1 Dec 2006 10:56:13 -0800	[thread overview]
Message-ID: <20061201105613.57821d87@freekitty> (raw)
In-Reply-To: <200612011340.kB1DeEhR014690@dut39.unminc.com>

Please don't mix whitespace and other fixes at same time.
Add a cleanup patch at beginning or end of series.

Please don't add other things like the driver name this in with bounce buffer
patch. Why the name change from netxen to netxen_nic?


> +/* Bounce buffer index */
> +struct bounce_index {
> +	/* Index of a buffer */
> +	unsigned buffer_index;
> +	/* Offset inside the buffer */
> +	unsigned buffer_offset;
> +};
> +
> +#define IS_BOUNCE 0xcafebb

Magic number? is this safe? why? there is a Documentation
file for these magic-number.txt.

> diff --git a/drivers/net/netxen/netxen_nic_isr.c b/drivers/net/netxen/netxen_nic_isr.c
> index ae180fe..f6ae9fd 100644
> --- a/drivers/net/netxen/netxen_nic_isr.c
> +++ b/drivers/net/netxen/netxen_nic_isr.c
> @@ -68,8 +68,7 @@ struct net_device_stats *netxen_nic_get_
>  void netxen_indicate_link_status(struct netxen_adapter *adapter, u32 portno,
>  				 u32 link)
>  {
> -	struct netxen_port *pport = adapter->port[portno];
> -	struct net_device *netdev = pport->netdev;
> +	struct net_device *netdev = (adapter->port[portno])->netdev;
>  

Parens unnecessary here.

-- 
Stephen Hemminger <shemminger@osdl.org>

  reply	other threads:[~2006-12-01 18:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-01 13:40 [PATCH 2/3] NetXen: 64-bit memory fixes Amit S. Kale
2006-12-01 18:56 ` Stephen Hemminger [this message]
2006-12-02  5:32 ` Jeff Garzik
2006-12-04 18:39   ` network devices don't handle pci_dma_mapping_error()'s Stephen Hemminger
2006-12-05  7:00     ` Muli Ben-Yehuda
2006-12-06 18:16       ` Stephen Hemminger
2006-12-06 19:33         ` Muli Ben-Yehuda
2006-12-07  6:18           ` Amit S. Kale
2006-12-07 13:04             ` Muli Ben-Yehuda
2006-12-07  0:54         ` David Miller
2006-12-07  0:58           ` Stephen Hemminger
2006-12-07  1:13             ` David Miller
2006-12-07  2:18               ` Rick Jones
2006-12-07  2:31                 ` David Miller
2006-12-07  6:25             ` Amit S. Kale
2006-12-07  6:46               ` Stephen Hemminger
2006-12-07  6:55                 ` Amit S. Kale
2006-12-07  7:24               ` David Miller
2006-12-07 20:07                 ` Stephen Hemminger

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=20061201105613.57821d87@freekitty \
    --to=shemminger@osdl.org \
    --cc=amitkale@netxen.com \
    --cc=brazilnut@us.ibm.com \
    --cc=jeff@garzik.org \
    --cc=netdev@vger.kernel.org \
    --cc=netxenproj@linsyssoft.com \
    --cc=rob@netxen.com \
    --cc=romieu@fr.zoreil.com \
    --cc=sanjeev@netxen.com \
    --cc=wendyx@us.ibm.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).