From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Florian Fainelli <f.fainelli@gmail.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@vger.kernel.org,
Gregory Clement <gregory.clement@free-electrons.com>
Subject: Re: linux-next: build warnings after merge of the net-next tree
Date: Tue, 22 Nov 2016 09:23:38 +0100 [thread overview]
Message-ID: <20161122092338.1b788f05@free-electrons.com> (raw)
In-Reply-To: <e5c5a4d7-355e-b8a6-9526-d6acbe4e54f8@gmail.com>
Hello,
On Mon, 21 Nov 2016 17:28:39 -0800, Florian Fainelli wrote:
> +Thomas, Gregory,
>
> On 11/21/2016 05:22 PM, Stephen Rothwell wrote:
> [snip]
> >
> > Introduced by commit
> >
> > a0627f776a45 ("net: marvell: Allow drivers to be built with COMPILE_TEST")
> >
> > "a few warnings" is a matter of perception. :-(
>
> Thomas, based on our IRC conversation, do you already have patches for
> mvneta and mvpp2 to build without warning on 64-bit or should I prepare
> patches for these?
Yes, we already have patches for making mvneta and mvpp2 build without
warning for 64-bit (Grégory for mvneta, and myself for mvpp2). I
intended to send the mvpp2 ones together with patches adding support
for a new variant of the IP, but I guess I can send just the few ones
that make it 64-bit "buildable".
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-22 8:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 1:22 linux-next: build warnings after merge of the net-next tree Stephen Rothwell
2016-11-22 1:28 ` Florian Fainelli
2016-11-22 8:23 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-04 4:47 Stephen Rothwell
2023-09-18 3:15 Stephen Rothwell
2023-09-18 7:43 ` Bagas Sanjaya
2023-06-26 6:29 Stephen Rothwell
2023-09-05 22:55 ` Stephen Rothwell
2023-09-05 23:44 ` Jakub Kicinski
2023-06-13 6:31 Stephen Rothwell
2023-06-20 16:15 ` Jakub Kicinski
2023-06-20 23:12 ` Saeed Mahameed
2022-11-14 7:31 Stephen Rothwell
2022-11-14 8:00 ` Akira Yokosawa
2021-06-15 11:23 Stephen Rothwell
2021-06-15 11:12 Stephen Rothwell
2021-03-18 6:22 Stephen Rothwell
2021-02-18 20:52 Stephen Rothwell
2021-02-19 8:44 ` Stephen Rothwell
2021-02-19 14:57 ` Kalle Valo
2020-12-14 9:10 Stephen Rothwell
2020-12-21 1:28 ` Stephen Rothwell
2021-01-05 6:19 ` Stephen Rothwell
2019-11-05 1:45 Stephen Rothwell
2017-03-20 6:07 Stephen Rothwell
2017-01-18 0:37 Stephen Rothwell
2015-06-20 13:12 Stephen Rothwell
2015-06-20 17:40 ` Florian Westphal
2015-06-20 18:31 ` Pablo Neira Ayuso
2015-05-14 7:12 Stephen Rothwell
2015-05-14 14:47 ` Willem de Bruijn
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=20161122092338.1b788f05@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=gregory.clement@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).