From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Parav Pandit <parav-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Roland Dreier <roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Is ib_mtu iboe_get_mtu() slightly off?
Date: Tue, 10 Oct 2017 18:33:12 +0300 [thread overview]
Message-ID: <20171010153312.GD2106@mtr-leonro.local> (raw)
In-Reply-To: <c27ee8b9-a011-9b0b-b20a-433d9f74d4b1-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
On Tue, Oct 10, 2017 at 10:48:01AM -0400, Doug Ledford wrote:
> On 10/9/2017 4:47 PM, Parav Pandit wrote:
>
> > Sorry for not ACKing that I was doing it last week.
> > If possible, please pick the one that Leon is sending because
> > instead of doing calculation in half comment based and half defined based code,
> > my patch defines all necessary header sizes in calculation, little clean way.
>
> In this instance we are lucky that 0day testing was being slow yesterday
> or else this would already be pushed to k.o. Since it's not, I can drop
> my patch and take yours.
Did you post your patch for review and gave enough time to participants
to provide the feedback, before pushing it to your k.o.?
Thanks
>
>
> --
> Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> GPG Key ID: B826A3330E572FDD
> Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-10 15:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 0:38 Is ib_mtu iboe_get_mtu() slightly off? Roland Dreier
[not found] ` <CAL1RGDX33tBR=x2sOp_F1605SY5nu_6YALr-XYE_LiuvsHQ1ng-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-21 2:20 ` Parav Pandit
[not found] ` <VI1PR0502MB300886CB47BB3DFDE098A26AD1660-o1MPJYiShExKsLr+rGaxW8DSnupUy6xnnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-10-09 13:34 ` Doug Ledford
[not found] ` <1507556073.46071.27.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-10-09 13:41 ` Leon Romanovsky
[not found] ` <20171009134131.GB1252-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-10-09 16:14 ` Doug Ledford
[not found] ` <1507565652.46071.33.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-10-09 20:47 ` Parav Pandit
[not found] ` <VI1PR0502MB3008900E038DEF6EEAB719DFD1740-o1MPJYiShExKsLr+rGaxW8DSnupUy6xnnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-10-10 14:48 ` Doug Ledford
[not found] ` <c27ee8b9-a011-9b0b-b20a-433d9f74d4b1-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-10-10 15:27 ` Parav Pandit
2017-10-10 15:33 ` Leon Romanovsky [this message]
[not found] ` <20171010153312.GD2106-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-10-10 16:13 ` Doug Ledford
2017-10-10 10:29 ` Amrani, Ram
[not found] ` <BN3PR07MB25781502CA573FB383805E48F8750-EldUQEzkDQfpW3VS/XPqkOFPX92sqiQdvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-10-10 15:26 ` Parav Pandit
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=20171010153312.GD2106@mtr-leonro.local \
--to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=parav-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=roland-BHEL68pLQRGGvPXPguhicg@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