All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Kees Cook <keescook@chromium.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] docs: Introduce deprecated APIs list
Date: Sun, 21 Oct 2018 17:11:50 +0200	[thread overview]
Message-ID: <CANiq72mh_3DsSWfTrUrz=XmBCNDFPFQGwxzzXD26h_-aGWxyiw@mail.gmail.com> (raw)
In-Reply-To: <20181017021708.GA22211@beast>

On Wed, Oct 17, 2018 at 4:20 AM Kees Cook <keescook@chromium.org> wrote:
>
> As discussed in the "API replacement/deprecation" thread[1], this
> makes an effort to document what things shouldn't get (re)added to the
> kernel, by introducing Documentation/process/deprecated.rst. It also
> adds the overflow kerndoc to ReST output, and tweaks the struct_size()
> documentation to parse correctly.

If you remember, please CC me as well, since I would like to be
involved in this as well, given that  it touches the compiler
attributes :-)

Also, I will send a patch (for the deprecated.rst file, adding a
section about fallthrough comments) later on.

Thanks for adding the file!

Cheers,
Miguel

      parent reply	other threads:[~2018-10-21 15:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17  2:17 [PATCH] docs: Introduce deprecated APIs list Kees Cook
2018-10-17  3:25 ` Randy Dunlap
2018-10-17 10:00   ` Jani Nikula
2018-10-17 17:08     ` Randy Dunlap
2018-10-17 22:37       ` Kees Cook
2018-10-17 22:41         ` Randy Dunlap
2018-10-17 23:34           ` Randy Dunlap
2018-10-17 12:50 ` Jonathan Corbet
2018-10-17 22:51   ` Kees Cook
2018-10-21 15:11 ` Miguel Ojeda [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='CANiq72mh_3DsSWfTrUrz=XmBCNDFPFQGwxzzXD26h_-aGWxyiw@mail.gmail.com' \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=corbet@lwn.net \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.