linux-kernel - Re: [PATCH v4 0/3] mfd: viperboard: fix cache line sharing and cleanups

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAE1zotLYqdV-m6XYo9QKndbyrEUAxgws5uqdNEs+CT_RcWeGHg@mail.gmail.com>
Date:	Thu, 9 Oct 2014 23:39:33 +0300
From:	Octavian Purdila <octavian.purdila@...el.com>
To:	Lee Jones <lee.jones@...aro.org>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	linux-usb@...r.kernel.org, Johan Hovold <johan@...nel.org>,
	Octavian Purdila <octavian.purdila@...el.com>
Subject: Re: [PATCH v4 0/3] mfd: viperboard: fix cache line sharing and cleanups

On Thu, Sep 25, 2014 at 6:41 PM, Octavian Purdila
<octavian.purdila@...el.com> wrote:
> Changes since v3:
>
>  * undo a whitespace change
>
>  * one more error path cleanup
>
>  * add commit body to the last patch
>
> Changes since v2:
>
>  * switch to using devm_ allocation
>
>  * remove unused platform_device
>
> Changes since v1:
>
>  * split cache sharing fix and cleanups into separate patches
>
>
> Octavian Purdila (3):
>   mfd: viperboard: allocate I/O buffer separately
>   mfd: viperboard: switch to devm_ allocation
>   mfd: viperboard: remove unused platform_device
>
>  drivers/mfd/viperboard.c       | 18 ++++++++----------
>  include/linux/mfd/viperboard.h |  3 +--
>  2 files changed, 9 insertions(+), 12 deletions(-)
>

Hi Lee,

Does these look ok now?

Thanks,
Tavi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/