From: David Miller <davem@davemloft.net>
To: diego.viola@gmail.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
cooldavid@cooldavid.org
Subject: Re: [PATCH] jme: remove the jme driver as it is no longer maintained
Date: Sat, 20 Feb 2016 19:16:59 -0500 (EST) [thread overview]
Message-ID: <20160220.191659.1399118945067159430.davem@davemloft.net> (raw)
In-Reply-To: <1456003203-10863-1-git-send-email-diego.viola@gmail.com>
Sorry, this is not how things work.
You can suggest marking the driver unmaintained in MAINTAINERS if the
listed developer has been unresponsive for a very long time.
But removing the driver altogether is not prudent at all.
Just because it doesn't work %100 the way you like, and nobody
has worked on fixing your specific problems, isn't a reason to
remove an entire driver _nor_ move it to -staging.
In fact, this driver is quite cleanly written, follows all of the
various coding style rules we have, and uses the vast majority of the
kernel APIs properly.
And those are the criteria for having something in staging, not that
it has bugs.
In fact it is so cleanly written, that you should be able to read it
and figure out what the suspend/resume problem might be. These are
exactly the kind of drivers we want to keep in the tree.
I'm sorry that your bugs didn't get fixed, but your response to that
happening is not reasonable at all.
next prev parent reply other threads:[~2016-02-21 0:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 21:20 [PATCH] jme: remove the jme driver as it is no longer maintained Diego Viola
2016-02-21 0:16 ` David Miller [this message]
2016-02-21 0:33 ` Diego Viola
[not found] ` <20160221124506.00237916@lxorguk.ukuu.org.uk>
2016-02-21 17:17 ` Diego Viola
2016-02-23 1:38 ` Diego Viola
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=20160220.191659.1399118945067159430.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cooldavid@cooldavid.org \
--cc=diego.viola@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).