From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch] nvme-rdma: fix an error code
Date: Wed, 13 Jul 2016 19:33:30 +0000 [thread overview]
Message-ID: <20160713193330.GW32247@mwanda> (raw)
In-Reply-To: <57866AE4.9040407@fb.com>
On Wed, Jul 13, 2016 at 09:23:00AM -0700, Jens Axboe wrote:
> On 07/13/2016 03:03 AM, Dan Carpenter wrote:
> >We accidentally return success when an error code was intended.
> >
> >Fixes: 711023071960 ('nvme-rdma: add a NVMe over Fabrics RDMA host driver')
> >Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> This is already fixed, what branch are you looking at?
>
Thanks.
Linux-next, but I wait a day before sending them out so I can review
them the next day. So yesterday's linux-next, I guess.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: dan.carpenter@oracle.com (Dan Carpenter)
Subject: [patch] nvme-rdma: fix an error code
Date: Wed, 13 Jul 2016 22:33:30 +0300 [thread overview]
Message-ID: <20160713193330.GW32247@mwanda> (raw)
In-Reply-To: <57866AE4.9040407@fb.com>
On Wed, Jul 13, 2016@09:23:00AM -0700, Jens Axboe wrote:
> On 07/13/2016 03:03 AM, Dan Carpenter wrote:
> >We accidentally return success when an error code was intended.
> >
> >Fixes: 711023071960 ('nvme-rdma: add a NVMe over Fabrics RDMA host driver')
> >Signed-off-by: Dan Carpenter <dan.carpenter at oracle.com>
>
> This is already fixed, what branch are you looking at?
>
Thanks.
Linux-next, but I wait a day before sending them out so I can review
them the next day. So yesterday's linux-next, I guess.
regards,
dan carpenter
next prev parent reply other threads:[~2016-07-13 19:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 10:03 [patch] nvme-rdma: fix an error code Dan Carpenter
2016-07-13 10:03 ` Dan Carpenter
2016-07-13 16:23 ` Jens Axboe
2016-07-13 16:23 ` Jens Axboe
2016-07-13 19:33 ` Dan Carpenter [this message]
2016-07-13 19:33 ` Dan Carpenter
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=20160713193330.GW32247@mwanda \
--to=dan.carpenter@oracle.com \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.