All of lore.kernel.org
 help / color / mirror / Atom feed
From: Prashant <prashant@broadcom.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <mchan@broadcom.com>
Subject: Re: [PATCH net-next] tg3: Override clock, link aware and link idle mode during NVRAM dump
Date: Sat, 24 May 2014 01:04:50 -0700	[thread overview]
Message-ID: <538052A2.1060700@broadcom.com> (raw)
In-Reply-To: <20140524.001739.1276621872731687446.davem@davemloft.net>



On 5/23/2014 9:17 PM, David Miller wrote:
> From: Prashant Sreedharan <prashant@broadcom.com>
> Date: Fri, 23 May 2014 09:54:44 -0700
>
>> +		if (cpmu_val & (CPMU_CTRL_LINK_AWARE_MODE |
>> +				CPMU_CTRL_LINK_IDLE_MODE)) {
>> +
>
> Please remove this empty line.
Ok
>
>> +			tw32(TG3_CPMU_CTRL, cpmu_val &
>> +			     ~(CPMU_CTRL_LINK_AWARE_MODE |
>> +			       CPMU_CTRL_LINK_IDLE_MODE));
>
> This is not indented correctly.
>
> The ~() expression is part of the "cpum_val &", it's not
> another separate argument to tw32().
>
> Therefore ~() should be indented to the column cpum_val starts
> at.
>
Will fix indentation.
>> +		if (need_resched()) {
>> +			if (signal_pending(current)) {
>> +				eeprom->len += i;
>> +				ret = -EINTR;
>> +				goto eeprom_done;
>
> Why are you incrementing eeprom->len when you break out of the
> loop due to a signal?  You didn't read that extra byte.
>
eeprom->len is discarded by caller if a failure is returned.
I will resend the patch after incorporating comments and add your 
Reviewed-by. Thanks.

  reply	other threads:[~2014-05-24  8:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 16:54 [PATCH net-next] tg3: Override clock, link aware and link idle mode during NVRAM dump Prashant Sreedharan
2014-05-24  4:17 ` David Miller
2014-05-24  8:04   ` Prashant [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-05-24  8:32 Prashant Sreedharan
2014-05-25  3:40 ` David Miller

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=538052A2.1060700@broadcom.com \
    --to=prashant@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=mchan@broadcom.com \
    --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.