public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: linux-s390@vger.kernel.org, linux-man@vger.kernel.org
Subject: Re: [man-pages PATCH 1/5] s390_runtime_instr.2: note that runtime_instr.h is not a public header
Date: Mon, 22 Jan 2018 15:11:05 +0000	[thread overview]
Message-ID: <20180122151105.GF4806@osiris> (raw)
In-Reply-To: <CACGkJduJ2SyWVZ7b-obLC_sB5TwHRfdpdfY5qDGrpzGgTC-H+A@mail.gmail.com>

On Mon, Jan 22, 2018 at 01:11:19PM +0000, Eugene Syromyatnikov wrote:
> On Sat, Jan 20, 2018 at 11:28 AM, Heiko Carstens
> <heiko.carstens@de.ibm.com> wrote:
> > IMHO we shouldn't document the file name of a kernel header that is not
> > exported. It's name and location can change anytime. I will move the kernel
> > header file to the uapi directory where it should have been since a long
> > time.
> 
> In that case, I think it could be rephrased to something like "the
> header asm/runtime_instr.h is available for the userspace programs
> since Linux 4.15, before that it was located in
> arch/s390/include/asm/runtime_instr.h in the kernel's source tree", as
> man-pages project (as I understood) tends to reference places in
> kernel's source tree if it is deemed useful; it is usually applied to
> documentation files, however, although they also have tendency to
> migrate over time.

Yes, that's ok. However moving the header file to uapi is not going to
happen before kernel version 4.16.

           reply	other threads:[~2018-01-22 15:11 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CACGkJduJ2SyWVZ7b-obLC_sB5TwHRfdpdfY5qDGrpzGgTC-H+A@mail.gmail.com>]

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=20180122151105.GF4806@osiris \
    --to=heiko.carstens@de.ibm.com \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-s390@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