linux-kernel - Re: [PATCH V3] gpio: samsung: use pr

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: <CACRpkdZCH_bxviyz5Qqx0ttFFGW-CkJT6vCT3-JcOgQ5quK0kg@mail.gmail.com>
Date:	Tue, 23 Oct 2012 00:16:20 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Jingoo Han <jg1.han@...sung.com>
Cc:	Grant Likely <grant.likely@...retlab.ca>,
	Kukjin Kim <kgene.kim@...sung.com>,
	linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
	Ryan Mallon <rmallon@...il.com>
Subject: Re: [PATCH V3] gpio: samsung: use pr_* instead of printk

On Mon, Oct 22, 2012 at 3:02 AM, Jingoo Han <jg1.han@...sung.com> wrote:
> On Friday, October 19, 2012 7:09 PM Linus Walleij wrote
>>
>> On Wed, Oct 17, 2012 at 3:52 AM, Jingoo Han <jg1.han@...sung.com> wrote:
>>
>> > This patch uses pr_* instead of printk. Also, gpio_dbg
>> > is replaced with pr_debug.
>> >
>> > Signed-off-by: Jingoo Han <jg1.han@...sung.com>
>> > Reviewed-by: Linus Walleij <linus.walleij@...aro.org> <- NAK
>>
>> Please consult Documentation/SubmittingPatches as to the conditions that
>> apply when you add Reviewed-by tags.
>
> Um, you already gave the Reviewed-by to the same patch, a month ago.
> Anyway, I will remove Reviewed-by and send v4 patch, soon.

My bad. I confused this mail thread for something else, sorry
for this. :-(

Please keep the Reviewed-tag if you want to!

Yours,
Linus Walleij (Now less confused)
--
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/