From: Sinan Kaya <okaya@codeaurora.org>
To: netdev@vger.kernel.org, timur@ocdeaurora.org, sulrich@ocdeaurora.org
Cc: linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
intel-wired-lan@lists.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/6] ixgbevf: keep writel() closer to wmb()
Date: Thu, 15 Mar 2018 21:13:10 -0400 [thread overview]
Message-ID: <98853dc0-694d-ab29-bf16-54fc5a05c7b8@codeaurora.org> (raw)
In-Reply-To: <1521162296-19729-6-git-send-email-okaya@codeaurora.org>
On 3/15/2018 9:04 PM, Sinan Kaya wrote:
> /* notify HW of packet */
> - ixgbevf_write_tail(tx_ring, i);
> + writel(value, tx_ring->tail);
>
oops. copy paste mistake.
I'll hold onto posting v3 until i hear more feedback.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
WARNING: multiple messages have this Message-ID (diff)
From: okaya@codeaurora.org (Sinan Kaya)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 5/6] ixgbevf: keep writel() closer to wmb()
Date: Thu, 15 Mar 2018 21:13:10 -0400 [thread overview]
Message-ID: <98853dc0-694d-ab29-bf16-54fc5a05c7b8@codeaurora.org> (raw)
In-Reply-To: <1521162296-19729-6-git-send-email-okaya@codeaurora.org>
On 3/15/2018 9:04 PM, Sinan Kaya wrote:
> /* notify HW of packet */
> - ixgbevf_write_tail(tx_ring, i);
> + writel(value, tx_ring->tail);
>
oops. copy paste mistake.
I'll hold onto posting v3 until i hear more feedback.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
WARNING: multiple messages have this Message-ID (diff)
From: Sinan Kaya <okaya@codeaurora.org>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v2 5/6] ixgbevf: keep writel() closer to wmb()
Date: Thu, 15 Mar 2018 21:13:10 -0400 [thread overview]
Message-ID: <98853dc0-694d-ab29-bf16-54fc5a05c7b8@codeaurora.org> (raw)
In-Reply-To: <1521162296-19729-6-git-send-email-okaya@codeaurora.org>
On 3/15/2018 9:04 PM, Sinan Kaya wrote:
> /* notify HW of packet */
> - ixgbevf_write_tail(tx_ring, i);
> + writel(value, tx_ring->tail);
>
oops. copy paste mistake.
I'll hold onto posting v3 until i hear more feedback.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2018-03-16 1:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 1:04 [PATCH v2 0/6] Eliminate duplicate barriers on weakly-ordered archs Sinan Kaya
2018-03-16 1:04 ` Sinan Kaya
2018-03-16 1:04 ` [PATCH v2 1/6] i40e/i40evf: " Sinan Kaya
2018-03-16 1:04 ` [Intel-wired-lan] " Sinan Kaya
2018-03-16 1:04 ` Sinan Kaya
2018-03-16 1:04 ` [PATCH v2 2/6] ixgbe: eliminate " Sinan Kaya
2018-03-16 1:04 ` [Intel-wired-lan] " Sinan Kaya
2018-03-16 1:04 ` Sinan Kaya
2018-03-16 1:04 ` [PATCH v2 3/6] igbvf: " Sinan Kaya
2018-03-16 1:04 ` [Intel-wired-lan] " Sinan Kaya
2018-03-16 1:04 ` Sinan Kaya
2018-03-16 1:04 ` [PATCH v2 4/6] igb: " Sinan Kaya
2018-03-16 1:04 ` [Intel-wired-lan] " Sinan Kaya
2018-03-16 1:04 ` Sinan Kaya
2018-03-16 1:04 ` [PATCH v2 5/6] ixgbevf: keep writel() closer to wmb() Sinan Kaya
2018-03-16 1:04 ` [Intel-wired-lan] " Sinan Kaya
2018-03-16 1:04 ` Sinan Kaya
2018-03-16 1:13 ` Sinan Kaya [this message]
2018-03-16 1:13 ` [Intel-wired-lan] " Sinan Kaya
2018-03-16 1:13 ` Sinan Kaya
2018-03-16 1:04 ` [PATCH v2 6/6] ixgbevf: eliminate duplicate barriers on weakly-ordered archs Sinan Kaya
2018-03-16 1:04 ` [Intel-wired-lan] " Sinan Kaya
2018-03-16 1:04 ` Sinan Kaya
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=98853dc0-694d-ab29-bf16-54fc5a05c7b8@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sulrich@ocdeaurora.org \
--cc=timur@ocdeaurora.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.