From: Brown, Aaron F <aaron.f.brown@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 2/3] igb: expose mailbox unlock method
Date: Fri, 14 Jul 2017 21:49:41 +0000 [thread overview]
Message-ID: <309B89C4C689E141A5FF6A0C5FB2118B8C64E01A@ORSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <20170628152226.25369-3-gedwards@ddn.com>
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at osuosl.org] On Behalf
> Of Greg Edwards
> Sent: Wednesday, June 28, 2017 8:22 AM
> To: intel-wired-lan at lists.osuosl.org
> Cc: Greg Edwards <gedwards@ddn.com>
> Subject: [Intel-wired-lan] [PATCH 2/3] igb: expose mailbox unlock method
>
> Add a mailbox unlock method to e1000_mbx_operations, which will be used
> to unlock the PF/VF mailbox by the PF.
>
> Signed-off-by: Greg Edwards <gedwards@ddn.com>
> ---
> drivers/net/ethernet/intel/igb/e1000_hw.h | 1 +
> drivers/net/ethernet/intel/igb/e1000_mbx.c | 39
> ++++++++++++++++++++++++++++++
> drivers/net/ethernet/intel/igb/e1000_mbx.h | 1 +
> 3 files changed, 41 insertions(+)
Tested-by: Aaron Brown <aaron.f.brown@intel.com>
next prev parent reply other threads:[~2017-07-14 21:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 15:22 [Intel-wired-lan] [PATCH 0/3] igb: VF mailbox timeouts with multiple VF messages Greg Edwards
2017-06-28 15:22 ` [Intel-wired-lan] [PATCH 1/3] igb: add argument names to mailbox op function declarations Greg Edwards
2017-07-14 21:49 ` Brown, Aaron F
2017-06-28 15:22 ` [Intel-wired-lan] [PATCH 2/3] igb: expose mailbox unlock method Greg Edwards
2017-07-14 21:49 ` Brown, Aaron F [this message]
2017-06-28 15:22 ` [Intel-wired-lan] [PATCH 3/3] igb: do not drop PF mailbox lock after read of VF message Greg Edwards
2017-07-14 21:50 ` Brown, Aaron F
2017-07-15 4:03 ` Alexander Duyck
2017-07-17 23:06 ` Greg Edwards
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=309B89C4C689E141A5FF6A0C5FB2118B8C64E01A@ORSMSX103.amr.corp.intel.com \
--to=aaron.f.brown@intel.com \
--cc=intel-wired-lan@osuosl.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.