public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Yuval Mintz <Yuval.Mintz@caviumnetworks.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, dan.carpenter@oracle.com
Subject: Re: [PATCH net 0/3] qed: Fix dependencies and warnings series
Date: Fri, 14 Oct 2016 08:51:09 +0200	[thread overview]
Message-ID: <8307648.oIx4xWhFox@wuerfel> (raw)
In-Reply-To: <1476388623-31032-1-git-send-email-Yuval.Mintz@caviumnetworks.com>

On Thursday, October 13, 2016 10:57:00 PM CEST Yuval Mintz wrote:
> Hi Dave,
> 
> The first patch in this series follows Dan Carpenter's reports about
> Smatch warnings for recent qed additions and fixes those.
> 
> The second patch is the most significant one [and the reason this is
> ntended for 'net'] - it's based on Arnd Bermann's suggestion for fixing
> compilation issues that were introduced with the roce addition as a result
> of certain combinations of qed, qede and qedr Kconfig options.
> 
> The third follows the discussion with Arnd and clears a lot of the warnings
> that arise when compiling the drivers with "C=1".
> 
> Please consider applying this series to 'net'.
> 

I've put all three patches into my randconfig test tree for double-checking,
but looking at the patches I'm fairly sure they are good.

I'll let you know within a few hours if something breaks unexpectedly.

Thanks for picking up my suggestions!

Acked-by: Arnd Bergmann <arnd@arndb.de>

  parent reply	other threads:[~2016-10-14  6:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-13 19:57 [PATCH net 0/3] qed: Fix dependencies and warnings series Yuval Mintz
2016-10-13 19:57 ` [PATCH net 1/3] qed: Fix static checker warning Yuval Mintz
2016-10-13 19:57 ` [PATCH net 2/3] qed*: Fix Kconfig dependencies with INFINIBAND_QEDR Yuval Mintz
2016-10-13 19:57 ` [PATCH net 3/3] qed: Additional work toward cleaning C=1 Yuval Mintz
2016-10-14  6:51 ` Arnd Bergmann [this message]
2016-10-14 15:07 ` [PATCH net 0/3] qed: Fix dependencies and warnings series David Miller

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=8307648.oIx4xWhFox@wuerfel \
    --to=arnd@arndb.de \
    --cc=Yuval.Mintz@caviumnetworks.com \
    --cc=dan.carpenter@oracle.com \
    --cc=davem@davemloft.net \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox