linux-kernel - Re: [PATCH] mfd: ti_am335x_tscadc: fix reg

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130813171644.GK15278@lee--X1>
Date:	Tue, 13 Aug 2013 18:16:44 +0100
From:	Lee Jones <lee.jones@...aro.org>
To:	Zubair Lutfullah <zubair.lutfullah@...il.com>
Cc:	sameo@...ux.intel.com, linux-kernel@...r.kernel.org,
	gregkh@...uxfoundation.org
Subject: Re: [PATCH] mfd: ti_am335x_tscadc: fix reg_cache in clr function

On Tue, 13 Aug 2013, Zubair Lutfullah wrote:

> Fixed reg_cache in the set function. But missed the clr function
> in the previous patch. This updates the clr function as well.
> 
> This applies after the previous fix I sent that Lee has accepted.
> mfd-next hasn't been updated yet.
> 
> 
> Zubair Lutfullah (1):
>   mfd: ti_am335x_tscadc: Update reg_cache variable in clr function
> 
>  drivers/mfd/ti_am335x_tscadc.c |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

I assume this is a 0/1 patch.

When you're sending a single patch, there's no need to send a front
page. Also, when you do send one, it's helpful to name the patches:

[PATCH 0/2] ...
[PATCH 1/2] ...
[PATCH 2/2] ...
... etc

Where 0/2 is the front page.

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
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/