From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: "Dmitry V. Levin" <ldv@altlinux.org>,
"David S. Miller" <davem@davemloft.net>,
Santosh Shilimkar <santosh.shilimkar@oracle.com>,
Sowmini Varadhan <sowmini.varadhan@oracle.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uapi: fix linux/rds.h userspace compilation errors
Date: Thu, 23 Feb 2017 14:20:24 +0300 [thread overview]
Message-ID: <46a28c0c-36fe-db81-d263-f737f1d3ea05@cogentembedded.com> (raw)
In-Reply-To: <20170223011320.GA16142@altlinux.org>
Hello!
On 2/23/2017 4:13 AM, Dmitry V. Levin wrote:
> Consistently use types from linux/types.h to fix the following
> linux/rds.h userspace compilation errors:
>
> /usr/include/linux/rds.h:198:2: error: unknown type name 'u8'
> u8 rx_traces;
> /usr/include/linux/rds.h:199:2: error: unknown type name 'u8'
> u8 rx_trace_pos[RDS_MSG_RX_DGRAM_TRACE_MAX];
> /usr/include/linux/rds.h:203:2: error: unknown type name 'u8'
> u8 rx_traces;
> /usr/include/linux/rds.h:204:2: error: unknown type name 'u8'
> u8 rx_trace_pos[RDS_MSG_RX_DGRAM_TRACE_MAX];
> /usr/include/linux/rds.h:205:2: error: unknown type name 'u64'
> u64 rx_trace[RDS_MSG_RX_DGRAM_TRACE_MAX];
>
> Fixes: 3289025a("RDS: add receive message trace used by application")
Need at least 12 hex digits and a space before (.
> Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>
[...]
MBR, Sergei
next prev parent reply other threads:[~2017-02-23 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 1:13 [PATCH] uapi: fix linux/rds.h userspace compilation errors Dmitry V. Levin
2017-02-23 1:40 ` Santosh Shilimkar
2017-02-23 11:20 ` Sergei Shtylyov [this message]
2017-02-23 11:35 ` [PATCH v2] " Dmitry V. Levin
2017-02-23 15:55 ` David Miller
[not found] <65dc4fe6-5363-3456-994e-166cb77a90cd@oracle.com>
2018-09-01 21:20 ` [PATCH] uapi: Fix " Vinson Lee
2018-09-02 23:15 ` 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=46a28c0c-36fe-db81-d263-f737f1d3ea05@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--cc=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=santosh.shilimkar@oracle.com \
--cc=sowmini.varadhan@oracle.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;
as well as URLs for NNTP newsgroup(s).