[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <12685471-6fcd-1f0f-c0d0-a09af2fc838e@denx.de>
Date: Fri, 21 Dec 2018 13:39:05 +0100
From: Marek Vasut <marex@...x.de>
To: Dan Carpenter <dan.carpenter@...cle.com>
Cc: Tristram.Ha@...rochip.com, pavel@...x.de, jiri@...nulli.us,
andrew@...n.ch, sergio.paracuellos@...il.com, f.fainelli@...il.com,
vivien.didelot@...oirfairelinux.com, UNGLinuxDriver@...rochip.com,
netdev@...r.kernel.org
Subject: Re: [PATCH v1 net-next] net: dsa: microchip: add KSZ9477 I2C driver
On 12/21/2018 01:23 PM, Dan Carpenter wrote:
> On Fri, Dec 21, 2018 at 01:14:51PM +0100, Marek Vasut wrote:
>> On 12/21/2018 10:29 AM, Dan Carpenter wrote:
>>> On Wed, Dec 19, 2018 at 10:50:16PM +0000, Tristram.Ha@...rochip.com wrote:
>>>>
>>>> So if I change the new code, should I go back to correct the old code?
>>>
>>> Other operating systems would worry about breaking code which is working
>>> fine, but re-writing ancient code is The Linux Way.
>>
>> So ... when will we finally rewrite Linux in rust ? :-)
>
> Probably we'll move more modules to userspace in time.
>
> Wasn't there a joke proof of concept a while back that let people write
> kernel modules in perl?
I recall seeing a couple different, more or less obscure, languages :)
--
Best regards,
Marek Vasut
Powered by blists - more mailing lists