mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH v2] fix ifru_data and ifcu_buf types in net/if.h
Date: Fri, 16 Sep 2016 18:00:14 -0400	[thread overview]
Message-ID: <20160916220014.GQ15995@brightrain.aerifal.cx> (raw)
In-Reply-To: <20160916173424.26062-1-dsabogal@ufl.edu>

On Fri, Sep 16, 2016 at 01:34:24PM -0400, Daniel Sabogal wrote:
> From: Daniel Sabogal <dsabogalcc@gmail.com>
> 
> glibc, freebsd, and openbsd use character pointers (caddr_t) for
> these fields. only linux uses void pointer for the ifru_data type.
> ---
>  include/net/if.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Thanks, applied.

Rich


      reply	other threads:[~2016-09-16 22:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-16 17:34 Daniel Sabogal
2016-09-16 22:00 ` Rich Felker [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=20160916220014.GQ15995@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).