From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 18 Apr 2012 09:01:35 +0200 From: Antonio Quartulli Message-ID: <20120418070134.GD27966@ritirata.org> References: <1334663907-22725-1-git-send-email-ordex@autistici.org> <1334663907-22725-11-git-send-email-ordex@autistici.org> <20120417.224746.802445483718191876.davem@davemloft.net> <20120418064659.GC27966@ritirata.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zS7rBR6csb6tI2e1" Content-Disposition: inline In-Reply-To: <20120418064659.GC27966@ritirata.org> Subject: Re: [B.A.T.M.A.N.] [PATCH 10/11] batman-adv: print OGM seq numbers as unsigned long Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Miller Cc: netdev@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.org --zS7rBR6csb6tI2e1 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 18, 2012 at 08:47:00AM +0200, Antonio Quartulli wrote: > On Tue, Apr 17, 2012 at 10:47:46 -0400, David Miller wrote: > > From: Antonio Quartulli > > Date: Tue, 17 Apr 2012 13:58:26 +0200 > >=20 > > > OGM sequence numbers are declared as uint32_t and so they have to pri= nted > > > using %u instead of %d in order to avoid wrong representations. > > >=20 > > > Signed-off-by: Antonio Quartulli > >=20 > > Fix this commit message subject, "%u" is "unsigned int" not > > "unsigned long" > >=20 > > "unsigned long" would be "%lu" There is a problem here. On my machine (x86_64) I have: typedef unsigned int __u32; typedef __u32 uint32_t; So I should use %u to print my uint32_t variable (as I reported in my commit message). Probably this is not the case on each and every architecture? If so, how could I handle it? Cheers, --=20 Antonio Quartulli =2E.each of us alone is worth nothing.. Ernesto "Che" Guevara --zS7rBR6csb6tI2e1 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQEcBAEBAgAGBQJPjmbOAAoJEFMQTLzJFOZFn+oIAKdeRG1o0X9VClIijzcMBqP9 4FR5ZQmXh2OTNixDc8owPguAg+oo32qB1ZyyWg8tskbkJaNuoAfOzTlNRzWuF8xa N9fv5bH1xn9FPG6YjW+T1lQAXGWV4yAVo39LcCiiVJd4Z5SpLTZJ8yZmpM+qv4cl WAg+FCa8v6DaP4i7YeSJBqyQhz3ExWQRHFO4q7bZBMTJdunM8vnETpTIEAfGNn4k BEr80hCcTmUDuGDchDZ/UVdcOPKFHoGOxzB1UXcO9mzIQPIcVK0UBL+MM+VT2vjA SlikullKy1EToe2cbC4zvcselJMQ726MGm3J8VPwU2curqVAsTUObVU0Zgtx52g= =k+pX -----END PGP SIGNATURE----- --zS7rBR6csb6tI2e1--