linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uapi: move forward declarations of internal structures
Date: Thu, 14 Jul 2016 01:44:20 +0300	[thread overview]
Message-ID: <20160713224420.GA15618@p183.telecom.by> (raw)
In-Reply-To: <20160713151557.a87f48b707f628c7cc5c6505@linux-foundation.org>

On Wed, Jul 13, 2016 at 03:15:57PM -0700, Andrew Morton wrote:
> On Thu, 14 Jul 2016 00:58:08 +0300 Alexey Dobriyan <adobriyan@gmail.com> wrote:
> 
> > Move "struct completion;".
> > Move "struct task_struct;".
> 
> That tells us no more than does the diff.
> 
> What's the reason for this change?  Any perceptible benefit?

You're right.

Changelog should be

Don't user forward declarations of internal kernel structures
in headers exported to userspace.

      reply	other threads:[~2016-07-13 22:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-13 21:58 [PATCH] uapi: move forward declarations of internal structures Alexey Dobriyan
2016-07-13 22:15 ` Andrew Morton
2016-07-13 22:44   ` Alexey Dobriyan [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=20160713224420.GA15618@p183.telecom.by \
    --to=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.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).