From: "Rustad, Mark D" <mark.d.rustad@intel.com>
To: David Miller <davem@davemloft.net>
Cc: "rick.jones2@hp.com" <rick.jones2@hp.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Compilation error on freshly pulled net-next?
Date: Fri, 5 Sep 2014 22:21:43 +0000 [thread overview]
Message-ID: <F30331BD-6C7F-418B-972F-6C4FD2E7D33A@intel.com> (raw)
In-Reply-To: <20140905.150901.79089716373802484.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
On Sep 5, 2014, at 3:09 PM, David Miller <davem@davemloft.net> wrote:
> From: Rick Jones <rick.jones2@hp.com>
> Date: Fri, 05 Sep 2014 14:47:43 -0700
>
>> Looks like someone slipped a J in there and confused things:
>>
>> + rtnl_port_size(dev, ext_filter_mask) /* IFLA_VF_PORTS +
>> IFLA_PORT_SELF */J + rtnl_link_get_size(dev) /* IFLA_LINKINFO */
>> + rtnl_link_get_af_size(dev) /* IFLA_AF_SPEC */
>>
>> (hopefully my mail client won't have mangled things too badly)
>>
>> What is odd though is a git diff after I've replaced that 'J' with a
>> return isn't giving me any output.
>
> That doesn't exist in my tree.
Looks like data corruption to me. There is a one-bit difference between line-feed and J. Oh for more ECC-capable systems...
--
Mark Rustad, Networking Division, Intel Corporation
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 841 bytes --]
prev parent reply other threads:[~2014-09-05 22:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 21:47 Compilation error on freshly pulled net-next? Rick Jones
2014-09-05 22:09 ` David Miller
2014-09-05 22:19 ` Rick Jones
2014-09-05 22:21 ` Rustad, Mark D [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=F30331BD-6C7F-418B-972F-6C4FD2E7D33A@intel.com \
--to=mark.d.rustad@intel.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.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