From: Randy Dunlap <rdunlap@xenotime.net>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: linux-next: Tree for Feb 15 (decnet)
Date: Wed, 15 Feb 2012 14:01:12 -0800 [thread overview]
Message-ID: <4F3C2B28.7030802@xenotime.net> (raw)
In-Reply-To: <20120215.163801.2243433584488421039.davem@davemloft.net>
On 02/15/2012 01:38 PM, David Miller wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
> Date: Wed, 15 Feb 2012 11:52:03 -0800
>
>> On 02/14/2012 09:03 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20120214:
>>
>>
>> on x86_64:
>>
>> CC net/decnet/dn_nsp_in.o
>> In file included from /next/linux-next-20120215/net/decnet/dn_nsp_in.c:75:0:
>> /next/linux-next-20120215/include/net/dn.h:195:65: warning: 'struct flowidn' declared inside parameter list
>
> I can't reproduce this in the net-next tree using your config but I can
> certainly fix it, as follows :-)
Yes, you fixed it. Thanks.
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
> --------------------
> decnet: net/dn.h needs net/flow.h
>
> Reported-by: Randy Dunlap <rdunlap@xenotime.net>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> ---
> include/net/dn.h | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/include/net/dn.h b/include/net/dn.h
> index 298521e..814af0b 100644
> --- a/include/net/dn.h
> +++ b/include/net/dn.h
> @@ -3,6 +3,7 @@
>
> #include <linux/dn.h>
> #include <net/sock.h>
> +#include <net/flow.h>
> #include <asm/byteorder.h>
> #include <asm/unaligned.h>
>
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2012-02-15 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120215160352.60be31b78879628be7e446b8@canb.auug.org.au>
2012-02-15 19:52 ` linux-next: Tree for Feb 15 (decnet) Randy Dunlap
2012-02-15 21:38 ` David Miller
2012-02-15 22:01 ` Randy Dunlap [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=4F3C2B28.7030802@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=davem@davemloft.net \
--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).