From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Devesh Sharma
<devesh.sharma-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
Jason Gunthorpe <jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH wip/dl-for-next] RDMA/bnxt_re: Fix kbuild error
Date: Thu, 18 Jan 2018 14:54:06 -0500 [thread overview]
Message-ID: <1516305246.3403.301.camel@redhat.com> (raw)
In-Reply-To: <CANjDDBgnhRuroVEfGJ=gF9=dS47w7pcQh5hZsF=p5iF6mxmX9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 724 bytes --]
On Thu, 2018-01-18 at 20:49 +0530, Devesh Sharma wrote:
> Hello Doug,
>
> Please pull this in, hopefully this will fix the latest build failure
> on your sub tree.
>
> -Regards
> Devesh
Hi Devesh,
Given that the code had only landed in my wip/ area, I took your patch
and squashed into the broken patch (which required a rebase) and then
pushed a new branch (wip/dl-for-next-rebased). We'll see if it passes
the tests there (it passed build tests on my local system the first
time, so just have to wait for the 0day results).
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-18 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 15:17 [PATCH wip/dl-for-next] RDMA/bnxt_re: Fix kbuild error Devesh Sharma
[not found] ` <1516288665-11055-1-git-send-email-devesh.sharma-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2018-01-18 15:19 ` Devesh Sharma
[not found] ` <CANjDDBgnhRuroVEfGJ=gF9=dS47w7pcQh5hZsF=p5iF6mxmX9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-18 19:54 ` Doug Ledford [this message]
[not found] ` <1516305246.3403.301.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-01-19 5:15 ` Devesh Sharma
2018-01-18 19:15 ` Yuval Shaia
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=1516305246.3403.301.camel@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=devesh.sharma-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
--cc=jgg-VPRAkNaXOzVWk0Htik3J/w@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 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.