From: Aishwarya Pant <aishpant@gmail.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
Greg KH <gregkh@linuxfoundation.org>,
linux-doc@vger.kernel.org, Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: [PATCH] Documentation/ABI: update infiniband sysfs interfaces
Date: Fri, 2 Feb 2018 13:56:59 +0530 [thread overview]
Message-ID: <20180202082659.GA1458@mordor.localdomain> (raw)
In-Reply-To: <20180201220811.GA17053@ziepe.ca>
On Thu, Feb 01, 2018 at 03:08:11PM -0700, Jason Gunthorpe wrote:
> On Thu, Feb 01, 2018 at 07:02:33PM +0530, Aishwarya Pant wrote:
> > Add documentation for core and hardware specific infiniband interfaces.
> > The descriptions have been collected from git commit logs, reading
> > through code and data sheets. Some drivers have incomplete doc and are
> > annotated with the comment '[to be documented]'.
> >
> > Signed-off-by: Aishwarya Pant <aishpant@gmail.com>
> > Documentation/ABI/testing/sysfs-class-infiniband | 755 +++++++++++++++++++++++
> > 1 file changed, 755 insertions(+)
>
> Wow this looks really great
>
> Should this patch delete some of the old documentation?
Yeah, I should do that because the documentation in
Documentation/infiniband/sysfs.txt is out of date.
>
> > diff --git a/Documentation/ABI/testing/sysfs-class-infiniband b/Documentation/ABI/testing/sysfs-class-infiniband
>
> Lots, maybe even all of of this is considered stable..
Okay, I guess it should belong to the stable directory then.
>
> > +sysfs interface for Broadcom NetXtreme-E RoCE driver
> > +----------------------------------------------------
> > +
> > +What: /sys/class/infiniband/bnxt_reX/fw_rev
> > +What: /sys/class/infiniband/bnxt_reX/hw_rev
> > +What: /sys/class/infiniband/bnxt_reX/hca_type
>
> These are actually common to all drivers
>
> /sys/class/infiniband/XXX/fw_rev, etc
Would make sense to define these at one place- hw_rev, hca_type, board_id are
common to a lot of the drivers.
Aishwarya
>
> Jason
prev parent reply other threads:[~2018-02-02 8:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 13:32 Aishwarya Pant
2018-02-01 17:48 ` Hal Rosenstock
2018-02-05 7:19 ` Aishwarya Pant
2018-02-05 13:16 ` Hal Rosenstock
2018-02-01 22:08 ` Jason Gunthorpe
2018-02-02 8:26 ` Aishwarya Pant [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=20180202082659.GA1458@mordor.localdomain \
--to=aishpant@gmail.com \
--cc=corbet@lwn.net \
--cc=dledford@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--cc=julia.lawall@lip6.fr \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@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
all inboxes | Powered by JetHome®