public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Sune Mølgaard" <sune@molgaard.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	gregkh@linuxfoundation.org
Subject: Re: [RFC] Summarizing deprecations
Date: Fri, 30 May 2014 23:00:56 -0400	[thread overview]
Message-ID: <20140531030055.GA8362@home.goodmis.org> (raw)
In-Reply-To: <53893895.3040202@molgaard.org>

On Sat, May 31, 2014 at 04:04:05AM +0200, Sune Mølgaard wrote:
> 
> As a user first, and only secondly a developer, I'd like my HW to work,
> and finding fully supported gear can still be hard if not impossible,
> but I imagine that if we had a central place to list deprecations (and,
> possibly, "victims" of them), a lot of grief could be avoided by simply
> pointing vendors to that central resource and saying "here is what you
> need to know for your driver to keep working - now get to it".

We had that. It was in the Documentation directory called "feature-removal.txt".
But that was always out of date and caused lots of unnecessary conflicts
by the few that added stuff to it that it became more of a pain to have than
it was worth. And commit 9c0ece069b32e8e122aea71aa47181c10eb85ba7 nuked it.

-- Steve


      parent reply	other threads:[~2014-05-31  3:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-31  2:04 [RFC] Summarizing deprecations Sune Mølgaard
2014-05-31  2:21 ` Greg KH
2014-05-31  2:56   ` Sune Mølgaard
2014-05-31  3:37     ` Greg KH
2014-06-02 23:12       ` Sune Mølgaard
2014-06-03  0:15         ` Greg KH
2014-05-31  3:00 ` Steven Rostedt [this message]

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=20140531030055.GA8362@home.goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sune@molgaard.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