linux-kernel - Re: [PATCH v2 PART-RESEND 0/2] berlin sdhci clock clean up

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: <566408ED.9040902@gmail.com>
Date:	Sun, 6 Dec 2015 11:07:41 +0100
From:	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
To:	Jisheng Zhang <jszhang@...vell.com>, robh+dt@...nel.org,
	pawel.moll@....com, mark.rutland@....com,
	ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
	linux@....linux.org.uk
Cc:	linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Mike Turquette <mturquette@...libre.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [PATCH v2 PART-RESEND 0/2] berlin sdhci clock clean up

On 19.11.2015 21:31, Sebastian Hesselbarth wrote:
> On 16.11.2015 11:56, Jisheng Zhang wrote:
>> Add or fix the optional clock property, then remove the CLK_IGNORE_UNUSED
>> flag for sdio clk(s).
>>
>> This is a partialy resend of 
>> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-October/379457.html
>>
>> patch3, patch4 has been merged.
> 
> Great! Really!
> 
> As they have been taken without my Acked-by, ignoring my request to
> _not_ remove the CLK_IGNORE_UNUSED flags _before_ these two, the
> remaining patches now become fixes.
> 
> Please resend the patches with a proper description what and why they
> are fixes now.

Is this going to be resolved anytime soon?

If not, I am going to send a revert for the CLK_IGNORE_UNUSED patch
and we start this from the beginning.

Sebastian

--
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/