netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: rmody@brocade.com
Cc: netdev@vger.kernel.org, adapter_linux_open_src_team@brocade.com
Subject: Re: [net-next 1/4] bna: Clear Driver Config Flags When HW Resets
Date: Sat, 11 May 2013 17:38:48 -0700 (PDT)	[thread overview]
Message-ID: <20130511.173848.1340042080692595063.davem@davemloft.net> (raw)
In-Reply-To: <1368205337-4624-2-git-send-email-rmody@brocade.com>

From: Rasesh Mody <rmody@brocade.com>
Date: Fri, 10 May 2013 10:02:14 -0700

>         Driver configuration flags are retained across open/stop operations
>         preventing configurations to be set in next open/stop.
>         Setting MTU on a 1020 causes network to fail until a reboot is performed
>         on the host.
> 
>         Clear the flags when configuration resets in hardware.

Please stop indenting your commit messages like this, nobody else
does this, so I cannot imagine where you observed this convention.

Resubmit this patch series with this corrected, thanks.

  reply	other threads:[~2013-05-12  0:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10 17:02 [net-next 0/4] Update the driver version to 3.2.21.1 Rasesh Mody
2013-05-10 17:02 ` [net-next 1/4] bna: Clear Driver Config Flags When HW Resets Rasesh Mody
2013-05-12  0:38   ` David Miller [this message]
2013-05-10 17:02 ` [net-next 2/4] bna: Fix Ucast Failure Handling Rasesh Mody
2013-05-10 17:02 ` [net-next 3/4] bna: Enahncement to Identify Default IOC Function Rasesh Mody
2013-05-10 17:02 ` [net-next 4/4] bna: Driver and Firmware Updated Rasesh Mody

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=20130511.173848.1340042080692595063.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=adapter_linux_open_src_team@brocade.com \
    --cc=netdev@vger.kernel.org \
    --cc=rmody@brocade.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).