diff for duplicates of <4D31CCFB.1060504@bfs.de> diff --git a/a/1.txt b/N1/1.txt index b7b9727..a646347 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -2,7 +2,7 @@ Am 15.01.2011 15:04, schrieb Dan Carpenter: > The signed one-bit types can be 0 or -1 which can cause a problem if -> someone ever checks if (foo->lu_gp_assoc = 1). The current code is +> someone ever checks if (foo->lu_gp_assoc == 1). The current code is > fine because everyone just checks zero vs non-zero. But Sparse > complains about it so lets change it. The warnings look like this: > diff --git a/a/content_digest b/N1/content_digest index 10b4ce5..8f51b04 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,7 +1,7 @@ "ref\020110115140445.GD2721@bicker\0" "From\0walter harms <wharms@bfs.de>\0" "Subject\0Re: [patch] [SCSI] target: dubious one-bit signed bitfield\0" - "Date\0Sat, 15 Jan 2011 16:36:11 +0000\0" + "Date\0Sat, 15 Jan 2011 17:36:11 +0100\0" "To\0Dan Carpenter <error27@gmail.com>" Nicholas A. Bellinger <nab@linux-iscsi.org> James Bottomley <James.Bottomley@suse.de> @@ -14,7 +14,7 @@ "\n" "Am 15.01.2011 15:04, schrieb Dan Carpenter:\n" "> The signed one-bit types can be 0 or -1 which can cause a problem if\n" - "> someone ever checks if (foo->lu_gp_assoc = 1). The current code is\n" + "> someone ever checks if (foo->lu_gp_assoc == 1). The current code is\n" "> fine because everyone just checks zero vs non-zero. But Sparse\n" "> complains about it so lets change it. The warnings look like this:\n" "> \n" @@ -118,4 +118,4 @@ "> \n" > -02529779fa2cf2e582711d762ef44f603851bc8fe18ab2e6824da7cb5140880d +ed1626d0e761fb108e381a4eb103ba221acc98f621fb1ff1b854e8f40f42b5d5
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.