From: Aishwarya Pant <aishpant@gmail.com>
To: Ozgur <ozgur@goosey.org>
Cc: Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Julia Lawall <julia.lawall@lip6.fr>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: Documentation: rapidio: move sysfs interface to ABI
Date: Mon, 8 Jan 2018 14:32:52 +0530 [thread overview]
Message-ID: <20180108090252.GA14572@mordor.localdomain> (raw)
In-Reply-To: <1498451515401892@web21g.yandex.ru>
On Mon, Jan 08, 2018 at 11:58:12AM +0300, Ozgur wrote:
>
>
> 08.01.2018, 11:38, "Aishwarya Pant" <aishpant@gmail.com>:
> > Hi
>
> Hello,
>
> > In Documentation/rapidio/sysfs.txt, there is a description of the sysfs
> > interface which could be moved to Documentation/ABI (as a bus interface under
> > testing).
> >
> > Would such a change be useful?
> >
> > The ABI documentation format looks like the following:
> >
> > What: (the full sysfs path of the attribute)
> > Date: (date of creation)
> > KernelVersion: (kernel version it first showed up in)
> > Contact: (primary contact)
> > Description: (long description on usage)
>
> Please you make the change you want after send your patch it diff format, right?
> I think a better decision can be made.
This is the idea. If this change is acceptable, then I can make a patch and send
it for review.
Aishwarya
>
> > I am doing this in an exercise to move sysfs ABI interfaces (which are
> > documented) to their right place i.e. in Documentation/ABI along with the rest.
> >
> > Aishwarya
>
> Regards
>
> Ozgur
next prev parent reply other threads:[~2018-01-08 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 8:38 Aishwarya Pant
2018-01-08 8:58 ` Ozgur
2018-01-08 9:02 ` Aishwarya Pant [this message]
2018-01-08 9:20 ` Ozgur
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=20180108090252.GA14572@mordor.localdomain \
--to=aishpant@gmail.com \
--cc=alexandre.bounine@idt.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@lip6.fr \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mporter@kernel.crashing.org \
--cc=ozgur@goosey.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
all inboxes | Powered by JetHome®