From: Selvin Xavier <selvin.xavier@broadcom.com>
To: Doug Ledford <dledford@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>,
linux-next@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Michael Chan <michael.chan@broadcom.com>,
Eddie Wai <eddie.wai@broadcom.com>,
Devesh Sharma <devesh.sharma@broadcom.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Subject: Re: linux-next: build failure after merge of the rdma tree
Date: Wed, 15 Feb 2017 10:39:44 +0530 [thread overview]
Message-ID: <CA+sbYW3GyZ1cf9NfdJTF6Pn-XcMW2cKMVxSycsnp62N-r0Pi9g@mail.gmail.com> (raw)
In-Reply-To: <ad8c1dc5-9d96-b45f-fe89-115ea4d0174c@redhat.com>
On Wed, Feb 15, 2017 at 6:35 AM, Doug Ledford <dledford@redhat.com> wrote:
>> From: Stephen Rothwell <sfr@canb.auug.org.au>
>> Date: Wed, 15 Feb 2017 11:23:25 +1100
>> Subject: [PATCH] RDMA/bnxt_re: fix for "bnxt_en: Update to firmware interface spec 1.7.0."
>>
>> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
>
> Thanks Stephen. I had been forewarned about this by Selvin and I
> instructed him to send me a fixup patch that would resolve the issue. I
> would apply it to my tree before merging with Linus. He just hadn't
> time to send it yet. Your patch is sufficient as well, so I may just
> pull it in. Thanks again.
Thanks Stephen and Doug for taking care of this.
Acked-by: Selvin Xavier <selvin.xavier@broadcom.com>
next prev parent reply other threads:[~2017-02-15 5:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 0:30 linux-next: build failure after merge of the rdma tree Stephen Rothwell
2017-02-15 1:05 ` Doug Ledford
2017-02-15 5:09 ` Selvin Xavier [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-01-13 1:35 Stephen Rothwell
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=CA+sbYW3GyZ1cf9NfdJTF6Pn-XcMW2cKMVxSycsnp62N-r0Pi9g@mail.gmail.com \
--to=selvin.xavier@broadcom.com \
--cc=davem@davemloft.net \
--cc=devesh.sharma@broadcom.com \
--cc=dledford@redhat.com \
--cc=eddie.wai@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=somnath.kotur@broadcom.com \
--cc=sriharsha.basavapatna@broadcom.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).