[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <804ed99e-257a-46b6-b453-86b215ef7309@DB9EHSMHS025.ehs.local>
Date: Mon, 2 Dec 2013 10:51:58 +0000
From: Srikanth Thokala <srikanth.thokala@...inx.com>
To: David Miller <davem@...emloft.net>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Michal Simek <michals@...inx.com>
Subject: RE: [PATCH 2/2] net: emaclite: add barriers to support Xilinx Zynq
platform
Hi David,
> -----Original Message-----
> From: David Miller [mailto:davem@...emloft.net]
> Sent: Monday, December 02, 2013 6:39 AM
> To: Srikanth Thokala
> Cc: netdev@...r.kernel.org; linux-arm-kernel@...ts.infradead.org; Michal
> Simek; Srikanth Thokala
> Subject: Re: [PATCH 2/2] net: emaclite: add barriers to support Xilinx Zynq
> platform
>
> From: Srikanth Thokala <srikanth.thokala@...inx.com>
> Date: Thu, 28 Nov 2013 12:59:57 +0530
>
> > This patch adds barriers at appropriate places to ensure the driver
> > works on Xilinx Zynq ARM-based SoC platform.
> >
> > Signed-off-by: Srikanth Thokala <sthokal@...inx.com>
>
> Memory barriers must have comments.
>
> Specifically, the comment must describe what exactly is being ensured by the
> memory barrier. What entity must see what memory operations in what order?
Ok. I will update and send you v2.
Thanks
Srikanth
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists