From: Jason Gunthorpe <jgg@ziepe.ca>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Yishai Hadas <yishaih@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
linux-netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH rdma-next v2 0/8] Support mlx5 flow steering with RAW data
Date: Wed, 25 Jul 2018 08:35:17 -0600 [thread overview]
Message-ID: <20180725143517.GU532@ziepe.ca> (raw)
In-Reply-To: <20180725053703.GK3189@mtr-leonro.mtl.com>
On Wed, Jul 25, 2018 at 08:37:03AM +0300, Leon Romanovsky wrote:
> > Also, I would like to keep the specs consistently formatted according
> > to clang-format with 'BinPackParameters: true', so I reflowed them as
> > well.
>
> I'm using default VIM clang-format.py without anything in .clang-format.
> Do you have an extra definitions there, except BinPackParameters?
These days Linux includes a top level .clang-format that does a
pretty good job.
I have to manually switch BinPackParameters on when working with these
specs to get the right indenting.. A pain, but maybe there is a better
way someday..
Jason
next prev parent reply other threads:[~2018-07-25 15:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 12:25 [PATCH rdma-next v2 0/8] Support mlx5 flow steering with RAW data Leon Romanovsky
2018-07-23 12:25 ` [PATCH mlx5-next v2 1/8] net/mlx5: Add forward compatible support for the FTE match data Leon Romanovsky
2018-07-23 21:05 ` Saeed Mahameed
2018-07-23 12:25 ` [PATCH mlx5-next v2 2/8] net/mlx5: Add support for flow table destination number Leon Romanovsky
2018-07-23 21:05 ` Saeed Mahameed
2018-07-23 12:25 ` [PATCH rdma-next v2 3/8] IB/mlx5: Introduce flow steering matcher object Leon Romanovsky
2018-07-23 12:25 ` [PATCH rdma-next v2 4/8] IB: Consider ib_flow creation by the KABI infrastructure Leon Romanovsky
2018-07-23 12:25 ` [PATCH rdma-next v2 5/8] IB/mlx5: Introduce vendor create and destroy flow methods Leon Romanovsky
2018-07-23 12:25 ` [PATCH rdma-next v2 6/8] IB/mlx5: Support adding flow steering rule by raw data Leon Romanovsky
2018-07-23 12:25 ` [PATCH rdma-next v2 7/8] IB/mlx5: Add support for a flow table destination Leon Romanovsky
2018-07-23 12:25 ` [PATCH rdma-next v2 8/8] IB/mlx5: Expose vendor flow trees Leon Romanovsky
2018-07-24 2:42 ` [PATCH rdma-next v2 0/8] Support mlx5 flow steering with RAW data Jason Gunthorpe
2018-07-24 5:56 ` Leon Romanovsky
2018-07-24 20:13 ` Jason Gunthorpe
2018-07-24 20:35 ` Jason Gunthorpe
2018-07-25 5:37 ` Leon Romanovsky
2018-07-25 14:35 ` Jason Gunthorpe [this message]
2018-07-26 4:35 ` Leon Romanovsky
2018-07-26 14:58 ` Jason Gunthorpe
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=20180725143517.GU532@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=yishaih@mellanox.com \
/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;
as well as URLs for NNTP newsgroup(s).