linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Federico Vaga <federico.vaga@vaga.pv.it>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Greg KH <greg@kroah.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc:process: remove note from 'stable api nonsense'
Date: Mon, 21 Jan 2019 09:14:00 +0100	[thread overview]
Message-ID: <53383524.y9DmdCAcNX@pcbe13614> (raw)
In-Reply-To: <20190120184338.01cd4ef9@lwn.net>

On Monday, January 21, 2019 2:43:38 AM CET Jonathan Corbet wrote:
> On Fri, 18 Jan 2019 22:58:04 +0100
> 
> Federico Vaga <federico.vaga@vaga.pv.it> wrote:
> > The link referred by the note can't be retrieved: this patch just
> > remove that old note.
> > 
> > Signed-off-by: Federico Vaga <federico.vaga@vaga.pv.it>
> > ---
> > 
> >  Documentation/process/stable-api-nonsense.rst | 3 +--
> >  1 file changed, 1 insertion(+), 2 deletions(-)
> > 
> > diff --git a/Documentation/process/stable-api-nonsense.rst
> > b/Documentation/process/stable-api-nonsense.rst index
> > 24f5aeecee91..57d95a49c096 100644
> > --- a/Documentation/process/stable-api-nonsense.rst
> > +++ b/Documentation/process/stable-api-nonsense.rst
> > @@ -171,8 +171,7 @@ is also a rough job.
> > 
> >  Simple, get your kernel driver into the main kernel tree (remember we
> >  are talking about GPL released drivers here, if your code doesn't fall
> > 
> > -under this category, good luck, you are on your own here, you leech
> > -<insert link to leech comment from Andrew and Linus here>.)  If your
> > +under this category, good luck, you are on your own here, you leech).  If
> > your> 
> >  driver is in the tree, and a kernel interface changes, it will be fixed
> >  up by the person who did the kernel change in the first place.  This
> >  ensures that your driver is always buildable, and works over time, with
> 
> I've applied this.  I do wonder if the "you leech" should maybe come out
> too, though.  I don't think that parasitic worms are a protected class
> under the CoC, but they might still suffer emotionally from being
> compared to the purveyors of proprietary modules...

I agree, do you want me to change the patch?

> 
> jon


-- 
Federico Vaga
http://www.federicovaga.it/



  reply	other threads:[~2019-01-21  8:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 21:58 [PATCH] doc:process: remove note from 'stable api nonsense' Federico Vaga
2019-01-19  8:32 ` Greg KH
2019-01-21  1:43 ` Jonathan Corbet
2019-01-21  8:14   ` Federico Vaga [this message]
2019-01-21  8:37     ` Greg KH
2019-01-22  9:17       ` Federico Vaga

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=53383524.y9DmdCAcNX@pcbe13614 \
    --to=federico.vaga@vaga.pv.it \
    --cc=corbet@lwn.net \
    --cc=greg@kroah.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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).