linux-kernel - Re: [PATCH 1/6] mmc: dw_mmc: remove the deprecated "clock-freq-min-max" property -- You wokr with japanese after they fucked you

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]

Date:   Mon, 26 Feb 2018 03:26:18 +0000
From:   thetruthbeforeus@...email.cc
To:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/6] mmc: dw_mmc: remove the deprecated
 "clock-freq-min-max" property -- You wokr with japanese after they fucked you

You all know that you're working with white and japanese mthr fuckers 
right? you just fine with that? After what they did to your people? Ok 
then. You be you. You be you.

Here's some real talk about the while mother fuckers:
https://www.liveleak.com/view?i=c34_1519605684

On 2018-02-26 02:07, Jaehoon Chung wrote:
> On 02/24/2018 01:16 AM, Andy Shevchenko wrote:
>> On Fri, Feb 23, 2018 at 4:19 PM, Shawn Lin <shawn.lin@...k-chips.com> 
>> wrote:
>>> On 2018/2/23 21:27, Andy Shevchenko wrote:
>>>> On Fri, Feb 23, 2018 at 8:41 AM, Jaehoon Chung 
>>>> <jh80.chung@...sung.com>
>>>> wrote:
>>>>> 
>>>>> 'clock-freq-min-max' property had already deprecated.
>>>>> Remove the 'clock-freq-min-max' property that is kept to maintain
>>>>> the compatibility.
>>>> 
>>>> 
>>>> Removing a property without telling the user what to expect is a bad
>>>> idea and ABI breakage.
>>>> 
>>> 
>>> What's the general process to remove a property?
>>> 
>>> I guess we should do:
>>> 1) deprecate it in the first place and remove it from all upstream DT
>>> 2) wait some long enough days for expecting the stale of all old DTB
>>> containing that property
>>> 3) remove the functionality of the deprecated property from the 
>>> driver
>>> but still leave some warning there
>>> 4) remove the left warning finally
>> 
>> I don't know. Perhaps Rob can shed a light here.
>> But I would really OK with removal of some of such properties from
>> some drivers where it's more burden to keep them.
> 
> This property had deprecated about 8months ago.
> I think that it was enough to keep this property for maintaining the
> compatibility.
> 
> I didn't remove this property without any alternative.
> 
> Best Regards,
> Jaehoon Chung
> 
>> 
>>> And for the ABI breakage, we should add something in 
>>> Documentation/ABI
>>> /obsolete  or Documentation/ABI/removed ?
>>