public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC rdma-next 2/3] IB/core: Export mlx5 vendor specific strucutres
Date: Thu, 15 Sep 2016 10:17:18 -0600	[thread overview]
Message-ID: <20160915161718.GD18154@obsidianresearch.com> (raw)
In-Reply-To: <20160915061336.GA4869-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>

On Wed, Sep 14, 2016 at 11:13:36PM -0700, Christoph Hellwig wrote:
> > index 4edb0f2..e804cc3 100644
> > +++ b/include/uapi/rdma/Kbuild
> > @@ -7,3 +7,4 @@ header-y += rdma_netlink.h
> >  header-y += rdma_user_cm.h
> >  header-y += hfi/
> >  header-y += rdma_user_rxe.h
> > +header-y += providers/
> 
> Can we avoid the horrible providers name?  The directories for drivers
> in the source tree so far are called hw/ and sw/ so we should stick to
> that here as well.

I also don't like the provider name, it is not consistent with Linux.

Not sure hw/sw is any better, other subsystems don't split their
drivers like that.

Just driver/?

Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-09-15 16:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14  8:27 [RFC rdma-next 0/3] Move mlx5 vendor specific to UAPI directory Leon Romanovsky
     [not found] ` <1473841649-8923-1-git-send-email-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-09-14  8:27   ` [RFC rdma-next 1/3] IB/mlx5: Move and decouple user vendor structures Leon Romanovsky
2016-09-14  8:27   ` [RFC rdma-next 2/3] IB/core: Export mlx5 vendor specific strucutres Leon Romanovsky
     [not found]     ` <1473841649-8923-3-git-send-email-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-09-15  6:13       ` Christoph Hellwig
     [not found]         ` <20160915061336.GA4869-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-09-15  6:25           ` Leon Romanovsky
2016-09-15 16:17           ` Jason Gunthorpe [this message]
2016-09-14  8:27   ` [RFC rdma-next 3/3] MAINTAINERS: Add mlx5 uapi file Leon Romanovsky
2016-09-14 17:21   ` [RFC rdma-next 0/3] Move mlx5 vendor specific to UAPI directory Jason Gunthorpe
     [not found]     ` <20160914172145.GI16014-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-09-14 19:46       ` Laurence Oberman
     [not found]         ` <1495514480.6044744.1473882367077.JavaMail.zimbra-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-09-15  5:06           ` Leon Romanovsky
2016-09-15  5:02       ` Leon Romanovsky

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=20160915161718.GD18154@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox