diff for duplicates of <200808211712.27146.arnd@arndb.de> diff --git a/a/1.txt b/N1/1.txt index ec2ace7..7c7b8c7 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -6,7 +6,7 @@ On Thursday 21 August 2008, Jared Hulbert wrote: > > We implemented a rwsem here because you can get concurrent readers. > My understanding is that downgrade_write() puts the rewem into the -> same state as down_read(). Â Am I mistaken? +> same state as down_read(). Am I mistaken? Your interpretation of downgrade_write is correct, but if every thread always does diff --git a/a/content_digest b/N1/content_digest index 3f809ff..7469cd9 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,13 +5,13 @@ "Subject\0Re: [PATCH 04/10] AXFS: axfs_inode.c\0" "Date\0Thu, 21 Aug 2008 17:12:26 +0200\0" "To\0Jared Hulbert <jaredeh@gmail.com>\0" - "Cc\0Linux-kernel@vger.kernel.org" + "Cc\0cotte@de.ibm.com" linux-embedded@vger.kernel.org - linux-mtd <linux-mtd@lists.infradead.org> + nickpiggin@yahoo.com.au " J\303\266rn Engel <joern@logfs.org>" - tim.bird@am.sony.com - cotte@de.ibm.com - " nickpiggin@yahoo.com.au\0" + Linux-kernel@vger.kernel.org + linux-mtd <linux-mtd@lists.infradead.org> + " tim.bird@am.sony.com\0" "\00:1\0" "b\0" "On Thursday 21 August 2008, Jared Hulbert wrote:\n" @@ -22,7 +22,7 @@ "> \n" "> We implemented a rwsem here because you can get concurrent readers.\n" "> My understanding is that downgrade_write() puts the rewem into the\n" - "> same state as down_read(). \303\202\302\240Am I mistaken?\n" + "> same state as down_read(). \302\240Am I mistaken?\n" "\n" "Your interpretation of downgrade_write is correct, but if every thread\n" "always does\n" @@ -44,4 +44,4 @@ "\n" "\tArnd <><" -3874165652750b9214405e8aae3fa522df92cb5cf22e4e980a4635be1fba4dcf +4d52872bb97d7c17586e0f3f0287d4638de4f5fb3fd9d4a921475ff4b874e5b7
diff --git a/a/1.txt b/N2/1.txt index ec2ace7..7c7b8c7 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -6,7 +6,7 @@ On Thursday 21 August 2008, Jared Hulbert wrote: > > We implemented a rwsem here because you can get concurrent readers. > My understanding is that downgrade_write() puts the rewem into the -> same state as down_read(). Â Am I mistaken? +> same state as down_read(). Am I mistaken? Your interpretation of downgrade_write is correct, but if every thread always does diff --git a/a/content_digest b/N2/content_digest index 3f809ff..a5e2849 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -22,7 +22,7 @@ "> \n" "> We implemented a rwsem here because you can get concurrent readers.\n" "> My understanding is that downgrade_write() puts the rewem into the\n" - "> same state as down_read(). \303\202\302\240Am I mistaken?\n" + "> same state as down_read(). \302\240Am I mistaken?\n" "\n" "Your interpretation of downgrade_write is correct, but if every thread\n" "always does\n" @@ -44,4 +44,4 @@ "\n" "\tArnd <><" -3874165652750b9214405e8aae3fa522df92cb5cf22e4e980a4635be1fba4dcf +b65d25ecfad8469d85ab78d416a543a762569909f9d7e0bd8797c6f79c7aac18
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.