From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Shannon Nelson <snelson@pensando.io>, netdev@vger.kernel.org
Subject: Re: ionic build issues?
Date: Thu, 19 Sep 2019 17:50:11 -0700 [thread overview]
Message-ID: <20190919175011.24fbf68d@cakuba.netronome.com> (raw)
In-Reply-To: <a99cf2d8-2479-2003-ac0b-10d44363c872@infradead.org>
On Thu, 19 Sep 2019 17:29:28 -0700, Randy Dunlap wrote:
> On 9/19/19 5:27 PM, Jakub Kicinski wrote:
> > Hi Shannon!
> >
> > I've enabled ionic to do some build testing before pushing patches
> > today, and with my tree which I build with W=1 C=1 I run into this:
> >
> > ../drivers/net/ethernet/pensando/ionic/ionic_main.c: In function ‘ionic_adminq_cb’:
> > ../drivers/net/ethernet/pensando/ionic/ionic_main.c:229:2: error: implicit declaration of function ‘dynamic_hex_dump’ [-Werror=implicit-function-declaration]
> > 229 | dynamic_hex_dump("comp ", DUMP_PREFIX_OFFSET, 16, 1,
> > | ^~~~~~~~~~~~~~~~
> > ../drivers/net/ethernet/pensando/ionic/ionic_lif.c: In function ‘ionic_notifyq_service’:
> > ../drivers/net/ethernet/pensando/ionic/ionic_lif.c:673:2: error: implicit declaration of function ‘dynamic_hex_dump’ [-Werror=implicit-function-declaration]
> > 673 | dynamic_hex_dump("event ", DUMP_PREFIX_OFFSET, 16, 1,
> > | ^~~~~~~~~~~~~~~~
> > cc1: some warnings being treated as errors
> >
> > Config attached, could you please take a look?
> >
>
> Patch is already posted.
> See https://lore.kernel.org/netdev/20190918195607.2080036-1-arnd@arndb.de/
Ah, thanks for pointing that out.
prev parent reply other threads:[~2019-09-20 0:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 0:27 ionic build issues? Jakub Kicinski
2019-09-20 0:29 ` Randy Dunlap
2019-09-20 0:50 ` Jakub Kicinski [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=20190919175011.24fbf68d@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=snelson@pensando.io \
/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).