netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>, davem@davemloft.net
Cc: Anjali Singhai Jain <anjali.singhai@intel.com>,
	netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
	jogreene@redhat.com
Subject: Re: [net-next 10/16] i40e: Fix the EMPR interrupt received handling
Date: Mon, 23 Feb 2015 15:45:18 +0300	[thread overview]
Message-ID: <54EB20DE.1010508@cogentembedded.com> (raw)
In-Reply-To: <1424661944-1779-11-git-send-email-jeffrey.t.kirsher@intel.com>

Hello.

On 2/23/2015 6:25 AM, Jeff Kirsher wrote:

> From: Anjali Singhai Jain <anjali.singhai@intel.com>

> We shouldn't trigger another EMPR when we receive an EMPR event.
> This patch handles EMPR event reception with a different state
> so that we can do the right thing for NVM.

> Change-ID: I9cac70b3658600f016a65beb6fb157e1c1f9adf9
> Signed-off-by: Anjali Singhai Jain <anjali.singhai@intel.com>
> Tested-by: Jim Young <james.m.young@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>

[...]

> diff --git a/drivers/net/ethernet/intel/i40e/i40e_main.c b/drivers/net/ethernet/intel/i40e/i40e_main.c
> index 2260cc1..0c1c38e 100644
> --- a/drivers/net/ethernet/intel/i40e/i40e_main.c
> +++ b/drivers/net/ethernet/intel/i40e/i40e_main.c

> @@ -6179,8 +6179,8 @@ static void i40e_reset_and_rebuild(struct i40e_pf *pf, bool reinit)
>   	}
>
>   	/* re-verify the eeprom if we just had an EMP reset */
> -	if (test_bit(__I40E_EMP_RESET_REQUESTED, &pf->state)) {
> -		clear_bit(__I40E_EMP_RESET_REQUESTED, &pf->state);
> +	if (test_bit(__I40E_EMP_RESET_INTR_RECEIVED, &pf->state)) {
> +		clear_bit(__I40E_EMP_RESET_INTR_RECEIVED, &pf->state);

    Why not use test_and_clear_bit()?

>   		i40e_verify_eeprom(pf);
>   	}

WBR, Sergei

  reply	other threads:[~2015-02-23 12:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23  3:25 [net-next 00/16][pull request] Intel Wired LAN Driver Updates 2015-02-22 Jeff Kirsher
2015-02-23  3:25 ` [net-next 01/16] e1000e: initial support for i219 Jeff Kirsher
2015-02-23  3:25 ` [net-next 02/16] igbvf: Fix code comments and whitespace Jeff Kirsher
2015-02-23  3:25 ` [net-next 03/16] igbvf: cleanup msleep() and min/max() usage Jeff Kirsher
2015-02-23  3:25 ` [net-next 04/16] i40e: update Shadow RAM read/write functions Jeff Kirsher
2015-02-23  3:25 ` [net-next 05/16] i40e: rename debugfs clear_stats option Jeff Kirsher
2015-02-23  3:25 ` [net-next 06/16] i40e/i40evf: Refactor the receive routines Jeff Kirsher
2015-02-23  3:25 ` [net-next 07/16] i40e/i40evf: restrict VC opcodes to their initial values Jeff Kirsher
2015-02-23  3:25 ` [net-next 08/16] i40e: Use #define for the VSI connection type Jeff Kirsher
2015-02-23  3:25 ` [net-next 09/16] i40e/i40evf: i40e_register.h updates Jeff Kirsher
2015-02-23  3:25 ` [net-next 10/16] i40e: Fix the EMPR interrupt received handling Jeff Kirsher
2015-02-23 12:45   ` Sergei Shtylyov [this message]
2015-02-23  3:25 ` [net-next 11/16] i40e/i40evf: Remove unused variable an_enable and function update_link_info Jeff Kirsher
2015-02-23  3:25 ` [net-next 12/16] i40e/i40evf: Bump Driver Versions Jeff Kirsher
2015-02-23  3:25 ` [net-next 13/16] i40e: Fix i40e_ndo_set_vf_spoofchk Jeff Kirsher
2015-02-23 17:18   ` Or Gerlitz
2015-02-23 17:31     ` Rose, Gregory V
2015-02-23 21:52       ` Or Gerlitz
2015-02-23 22:00         ` Rose, Gregory V
2015-02-24  9:19           ` Or Gerlitz
2015-02-24 16:00             ` Rose, Gregory V
2015-02-23  3:25 ` [net-next 14/16] i40evf: disable NAPI polling sooner Jeff Kirsher
2015-02-23  3:25 ` [net-next 15/16] i40evf: refactor reset Jeff Kirsher
2015-02-23  3:25 ` [net-next 16/16] i40evf: don't wait forever Jeff Kirsher
2015-02-23 20:03 ` [net-next 00/16][pull request] Intel Wired LAN Driver Updates 2015-02-22 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=54EB20DE.1010508@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=anjali.singhai@intel.com \
    --cc=davem@davemloft.net \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jogreene@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@redhat.com \
    --cc=sassmann@redhat.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).