All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: add Kernel Driver Statement to the kernel
Date: Fri, 6 Oct 2017 11:44:15 -0300	[thread overview]
Message-ID: <20171006114415.303ff337@recife.lan> (raw)
In-Reply-To: <20171006091038.GA16038@kroah.com>

Em Fri, 6 Oct 2017 11:10:38 +0200
Greg Kroah-Hartman <gregkh@linuxfoundation.org> escreveu:

> Way back in 2008 we didn't have "robust" in-kernel documentation system,
> so the idea of putting something like the kernel driver statement in the
> kernel tree wasn't even imagined.  But now that has changed, so add the
> old document to the kernel source itself to allow for us to properly
> reference it in one canonical place (as the LF wiki keeps moving things
> around.)
> 
> This also will allow people to add their names to it, as I seem to have
> lost the ability to do that by not knowing how to edit things on the
> original document.
> 
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

>From my side:

Acked-by: Mauro Carvalho Chehab <mchehab@kernel.org>


Thanks,
Mauro

  reply	other threads:[~2017-10-06 14:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-06  9:10 [PATCH] Documentation: add Kernel Driver Statement to the kernel Greg Kroah-Hartman
2017-10-06 14:44 ` Mauro Carvalho Chehab [this message]
2017-10-06 15:03 ` Jonathan Corbet
2017-10-14 16:14 ` Wolfram Sang
2017-10-14 16:26   ` gregkh
2017-10-14 18:09     ` Wolfram Sang
2017-10-14 19:50       ` gregkh
2017-10-16 14:19         ` Jani Nikula

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=20171006114415.303ff337@recife.lan \
    --to=mchehab@infradead.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.