All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] net: Make sure IPaddr_t is 32 bits in size
Date: Tue, 06 Dec 2011 22:15:40 +0100	[thread overview]
Message-ID: <20111206211540.DC5E61A32821@gemini.denx.de> (raw)
In-Reply-To: <1322918984-9089-1-git-send-email-weisserm@arcor.de>

Dear Matthias Weisser,

In message <1322918984-9089-1-git-send-email-weisserm@arcor.de> you wrote:
> When building u-boot as 64 bit application (e.g. sandbox) ulong might be
> 64 bits in size. This breaks network code as IPaddr_t is 64 bytes in
> size then and an IPv4 address is 32 bits in size. This patch makes sure
> that IPaddr_t is always 32 bits in size. Also some warnings introduced
> by this patch are fixed.
> 
> Signed-off-by: Matthias Weisser <weisserm@arcor.de>
> Acked-by: Mike Frysinger <vapier@gentoo.org>
> ---
> Changes in v2:
>   Added explicit information about 32 bit size of IPv4 addresses in
>   commit message and source comment.
> 
>  include/net.h |    3 ++-
>  net/net.c     |    6 +++---
>  net/nfs.c     |    2 +-
>  net/tftp.c    |    2 +-
>  4 files changed, 7 insertions(+), 6 deletions(-)

Applied, thanks.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The one who says it cannot be done should never interrupt the one who
is doing it.

      reply	other threads:[~2011-12-06 21:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02 16:26 [U-Boot] [PATCH] net: Make sure IPaddr_t is 32 bits in size Matthias Weisser
2011-12-02 16:47 ` Mike Frysinger
2011-12-02 16:48 ` Mike Frysinger
2011-12-03 13:29 ` [U-Boot] [PATCH V2] " Matthias Weisser
2011-12-06 21:15   ` Wolfgang Denk [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=20111206211540.DC5E61A32821@gemini.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.