From: Dan Carpenter <dan.carpenter@oracle.com>
To: Marek Vasut <marex@denx.de>
Cc: Tristram.Ha@microchip.com, pavel@denx.de, jiri@resnulli.us,
andrew@lunn.ch, sergio.paracuellos@gmail.com,
f.fainelli@gmail.com, vivien.didelot@savoirfairelinux.com,
UNGLinuxDriver@microchip.com, netdev@vger.kernel.org
Subject: Re: [PATCH v1 net-next] net: dsa: microchip: add KSZ9477 I2C driver
Date: Fri, 21 Dec 2018 15:23:44 +0300 [thread overview]
Message-ID: <20181221122344.GE2240@kadam> (raw)
In-Reply-To: <0c32ce3b-0763-f96e-5d47-df5418f91df2@denx.de>
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@microchip.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?
regards,
dan carpenter
next prev parent reply other threads:[~2018-12-21 12:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 3:41 [PATCH v1 net-next] net: dsa: microchip: add KSZ9477 I2C driver Tristram.Ha
2018-12-19 4:31 ` Woojung.Huh
2018-12-19 22:59 ` Tristram.Ha
2018-12-19 23:19 ` Woojung.Huh
2018-12-19 8:09 ` Marek Vasut
2018-12-19 22:30 ` Tristram.Ha
2018-12-19 23:11 ` Marek Vasut
2018-12-19 23:31 ` Marek Vasut
2018-12-20 1:10 ` Marek Vasut
2018-12-21 0:48 ` Tristram.Ha
2018-12-21 2:03 ` Marek Vasut
2018-12-19 10:05 ` Jiri Pirko
2018-12-19 16:08 ` Pavel Machek
2018-12-19 16:15 ` Jiri Pirko
2018-12-19 17:22 ` Pavel Machek
2018-12-19 17:24 ` Marek Vasut
2018-12-19 22:50 ` Tristram.Ha
2018-12-19 23:12 ` Marek Vasut
2018-12-21 9:29 ` Dan Carpenter
2018-12-21 12:14 ` Marek Vasut
2018-12-21 12:23 ` Dan Carpenter [this message]
2018-12-21 12:39 ` Marek Vasut
2019-01-09 16:05 ` Pavel Machek
2019-01-09 16:15 ` Marek Vasut
2018-12-19 16:45 ` David Miller
2019-01-10 8:15 ` Sergio Paracuellos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181221122344.GE2240@kadam \
--to=dan.carpenter@oracle.com \
--cc=Tristram.Ha@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=jiri@resnulli.us \
--cc=marex@denx.de \
--cc=netdev@vger.kernel.org \
--cc=pavel@denx.de \
--cc=sergio.paracuellos@gmail.com \
--cc=vivien.didelot@savoirfairelinux.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).