diff for duplicates of <20090122065104.2787df2d.akpm@linux-foundation.org> diff --git a/a/1.txt b/N1/1.txt index 98c2ec6..e22cddf 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,4 +1,4 @@ -> On Thu, 15 Jan 2009 15:32:11 -0700 Jonathan Corbet <corbet-T1hC0tSOHrs@public.gmane.org> wrote: +> On Thu, 15 Jan 2009 15:32:11 -0700 Jonathan Corbet <corbet@lwn.net> wrote: > One of these years I've got to get this right. I've fixed the problem > pointed out by Oleg where f_flags would get changed even if fasync() > fails. @@ -30,7 +30,7 @@ scream. > f_op->fasync() need to be done in an atomic manner. Here, the BKL is > removed and FASYNC modifications are protected with a mutex. > -> Signed-off-by: Jonathan Corbet <corbet-T1hC0tSOHrs@public.gmane.org> +> Signed-off-by: Jonathan Corbet <corbet@lwn.net> > --- > drivers/char/tty_io.c | 5 +-- > fs/fcntl.c | 65 +++++++++++++++++++++++++++++++++++++++---------- @@ -115,9 +115,3 @@ column zero, please. It isn't completely obvious what fasync_mutex is protecting, why it exists. A comment which explains this would be appropriate? - - --- -To unsubscribe from this list: send the line "unsubscribe linux-api" in -the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org -More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 787b0ec..9b2ef38 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,18 +1,17 @@ "ref\020090115153211.663df310@bike.lwn.net\0" - "ref\020090115153211.663df310-vw3g6Xz/EtPk1uMJSBkQmQ@public.gmane.org\0" - "From\0Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>\0" + "From\0Andrew Morton <akpm@linux-foundation.org>\0" "Subject\0Re: [PATCH, RFC] Remove fasync() BKL usage, take 3325\0" "Date\0Thu, 22 Jan 2009 06:51:04 -0800\0" - "To\0Jonathan Corbet <corbet-T1hC0tSOHrs@public.gmane.org>\0" - "Cc\0linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" - andi-Vw/NltI1exuRpAAqCnN02g@public.gmane.org - viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org - oleg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org - linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org - " alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org\0" + "To\0Jonathan Corbet <corbet@lwn.net>\0" + "Cc\0linux-kernel@vger.kernel.org" + andi@firstfloor.org + viro@zeniv.linux.org.uk + oleg@redhat.com + linux-api@vger.kernel.org + " alan@lxorguk.ukuu.org.uk\0" "\00:1\0" "b\0" - "> On Thu, 15 Jan 2009 15:32:11 -0700 Jonathan Corbet <corbet-T1hC0tSOHrs@public.gmane.org> wrote:\n" + "> On Thu, 15 Jan 2009 15:32:11 -0700 Jonathan Corbet <corbet@lwn.net> wrote:\n" "> One of these years I've got to get this right. I've fixed the problem\n" "> pointed out by Oleg where f_flags would get changed even if fasync()\n" "> fails. \n" @@ -44,7 +43,7 @@ "> f_op->fasync() need to be done in an atomic manner. Here, the BKL is\n" "> removed and FASYNC modifications are protected with a mutex.\n" "> \n" - "> Signed-off-by: Jonathan Corbet <corbet-T1hC0tSOHrs@public.gmane.org>\n" + "> Signed-off-by: Jonathan Corbet <corbet@lwn.net>\n" "> ---\n" "> drivers/char/tty_io.c | 5 +--\n" "> fs/fcntl.c | 65 +++++++++++++++++++++++++++++++++++++++----------\n" @@ -128,12 +127,6 @@ "\n" "It isn't completely obvious what fasync_mutex is protecting, why it exists.\n" "\n" - "A comment which explains this would be appropriate?\n" - "\n" - "\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-api\" in\n" - "the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + A comment which explains this would be appropriate? -87802892acccb8d96401b5e721ea6a29d3ea5a77f5b8b51d5b5857c9e33b0592 +b62e513acebde56818d60d8ec8c0318b0f39d5af5ae295b966bf46f8f94e7fd1
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.