From: Heiko Carstens <heiko.carstens-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
To: Eugene Syromyatnikov <evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Michael Kerrisk-manpages
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Martin Schwidefsky
<schwidefsky-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>,
linux-s390-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
QingFeng Hao
<haoqf-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.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 16:11:05 +0100 [thread overview]
Message-ID: <20180122151105.GF4806@osiris> (raw)
In-Reply-To: <CACGkJduJ2SyWVZ7b-obLC_sB5TwHRfdpdfY5qDGrpzGgTC-H+A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
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.
next prev parent reply other threads:[~2018-01-22 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 18:56 [man-pages PATCH 1/5] s390_runtime_instr.2: note that runtime_instr.h is not a public header Eugene Syromyatnikov
[not found] ` <20180114185622.GA23506-ZbobWygYI+YXGNroddHbYwC/G2K4zDHf@public.gmane.org>
2018-01-20 11:28 ` Heiko Carstens
2018-01-22 13:11 ` Eugene Syromyatnikov
[not found] ` <CACGkJduJ2SyWVZ7b-obLC_sB5TwHRfdpdfY5qDGrpzGgTC-H+A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-22 15:11 ` Heiko Carstens [this message]
2018-01-22 15:11 ` Heiko Carstens
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-ta70fqpds9bqt0dzr+alfa@public.gmane.org \
--cc=evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=haoqf-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-s390-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=schwidefsky-tA70FqPdS9bQT0dZR+AlfA@public.gmane.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.