From: David Miller <davem@davemloft.net>
To: Yuval.Mintz@cavium.com
Cc: netdev@vger.kernel.org, richardcochran@gmail.com,
Sudarsana.Kalluru@cavium.com
Subject: Re: [PATCH net-next v6 0/2] qed*: Add support for PTP
Date: Tue, 14 Feb 2017 15:14:20 -0500 (EST) [thread overview]
Message-ID: <20170214.151420.31347870149815362.davem@davemloft.net> (raw)
In-Reply-To: <BL2PR07MB230680F7B0E85799B0DA58C48D580@BL2PR07MB2306.namprd07.prod.outlook.com>
From: "Mintz, Yuval" <Yuval.Mintz@cavium.com>
Date: Tue, 14 Feb 2017 20:12:52 +0000
>> > This patch series adds required changes for qed/qede drivers for
>> > supporting the IEEE Precision Time Protocol (PTP).
>> >
>> > Dave,
>> > Please consider applying this series to "net-next".
>
>> Please fix the problems reported by the kbuild robot.
>
>> Thanks.
>
> Fixing those are trivial [simply setting the variables to 0 on declaration],
> but I actually believe those are false positives.
> Still, if you want me to re-spin v7 for this - I'll send it tomorrow.
Yes I want you to respin. If the kbuild robot reports something you have
to fix it up.
prev parent reply other threads:[~2017-02-14 20:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 16:03 [PATCH net-next v6 0/2] qed*: Add support for PTP Yuval Mintz
2017-02-14 16:03 ` [PATCH net-next v6 1/2] qed: Add infrastructure for PTP support Yuval Mintz
2017-02-14 19:20 ` kbuild test robot
2017-02-14 16:03 ` [PATCH net-next v6 2/2] qede: Add driver support for PTP Yuval Mintz
2017-02-14 18:30 ` [PATCH net-next v6 0/2] qed*: Add " Richard Cochran
2017-02-14 19:43 ` David Miller
2017-02-14 20:12 ` Mintz, Yuval
2017-02-14 20:14 ` David Miller [this message]
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=20170214.151420.31347870149815362.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Sudarsana.Kalluru@cavium.com \
--cc=Yuval.Mintz@cavium.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.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).