From: Jeff Garzik <jgarzik@pobox.com>
To: Jesse Huang <jesse@icplus.com.tw>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH 5/6] IP100A correct init and close step
Date: Thu, 17 Aug 2006 10:51:45 -0400 [thread overview]
Message-ID: <44E48281.1060504@pobox.com> (raw)
In-Reply-To: <1155841712.4532.19.camel@localhost.localdomain>
Jesse Huang wrote:
> From: Jesse Huang <jesse@icplus.com.tw>
>
> correct init and close step
>
> Change Logs:
> correct init and close step
>
> ---
>
> drivers/net/sundance.c | 10 +++++++++-
> 1 files changed, 9 insertions(+), 1 deletions(-)
>
> b5e343a17f5d70d1cc9a4ba20d366bab355f64a6
> diff --git a/drivers/net/sundance.c b/drivers/net/sundance.c
> index f63871a..c7c22f0 100755
> --- a/drivers/net/sundance.c
> +++ b/drivers/net/sundance.c
> @@ -830,6 +830,11 @@ #endif
> iowrite8(0x01, ioaddr + DebugCtrl1);
> netif_start_queue(dev);
>
> + // 04/19/2005 Jesse fix for complete initial step
> + spin_lock(&np->lock);
> + reset_tx(dev);
> + spin_unlock(&np->lock);
> +
NAK -- ineffective locking.
If you need locking here, you must use spin_lock_irqsave()
> @@ -1654,7 +1659,10 @@ static int netdev_close(struct net_devic
>
> /* Disable interrupts by clearing the interrupt mask. */
> iowrite16(0x0000, ioaddr + IntrEnable);
> -
> +
> + // 04/19/2005 Jesse fix for complete initial step
> + writew(0x500, ioaddr + DMACtrl);
NAK:
1) date and author information is already present in the kernel
changelog. It should not be present in the source code.
2) The comment (or patch description) fails to describe -why- this
change is needed. It only described what is being changes, which is
already obvious from reading the source code.
next prev parent reply other threads:[~2006-08-17 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 19:08 [PATCH 5/6] IP100A correct init and close step Jesse Huang
2006-08-17 14:51 ` Jeff Garzik [this message]
2006-08-18 6:11 ` Jesse Huang
2006-08-18 11:12 ` Jeff Garzik
2006-08-21 3:37 ` Jesse Huang
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=44E48281.1060504@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=jesse@icplus.com.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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.