diff for duplicates of <5140C6B2.7040702@gmail.com> diff --git a/a/1.txt b/N1/1.txt index 3e12a4f..c8d28cd 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -55,11 +55,11 @@ Daniel > sources (requested without success). > > drivers/char/mxser.c drivers/char/mxser.h: MOXA -> SMARTIO/INDUSTIO/INTELLIO SERIAL CARD (Jiří Slabý): +> SMARTIO/INDUSTIO/INTELLIO SERIAL CARD (Ji?? Slab?): > Force board setup for CONFIG_ARCH_MOXART. > ASYNCB_CLOSING is avoided because of a lockup (infinite wait after > tty_wait_until_sent). Why this happens is unknown (to me) I'm hoping -> someone (Jiří?) can shed light. SysRq trace @ http://ideone.com/e845mr +> someone (Ji???) can shed light. SysRq trace @ http://ideone.com/e845mr > What significance does ASYNCB_CLOSING have? > Obviously, automatic detection is better but "mxser_read_register" is > pointless on this hardware. What to do instead? Is it better to make a @@ -83,7 +83,7 @@ Daniel > https://linux-2-6-34-14-moxart.googlecode.com/files/linux-2.6.34.14-moxart.patch > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in -> the body of a message to majordomo@vger.kernel.org +> the body of a message to majordomo at vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > diff --git a/a/content_digest b/N1/content_digest index 9e613bb..4db58a6 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,15 +1,10 @@ "ref\0CACmBeS1NLFUYHBOVL28aCCzRrgXYGPZF9t3qj6AdcgaMkrPGoQ@mail.gmail.com\0" "ref\0CACmBeS01vs=fHOXu1Lnq8GX8YAbF6aBKmqopKPVt78mPYm=_9w@mail.gmail.com\0" "ref\0CACmBeS05cyT8N9nZeqbJUPMSGeZYLWjL0Tu1GSZ-ms+Hjc0UoQ@mail.gmail.com\0" - "From\0Daniel Mack <zonque@gmail.com>\0" - "Subject\0Re: [PATCH] ARM: mach-moxart: platform port for MOXA ART SoC\0" + "From\0zonque@gmail.com (Daniel Mack)\0" + "Subject\0[PATCH] ARM: mach-moxart: platform port for MOXA ART SoC\0" "Date\0Wed, 13 Mar 2013 19:34:26 +0100\0" - "To\0Jonas Jensen <jonas.jensen@gmail.com>\0" - "Cc\0linux-arm-kernel@lists.infradead.org" - linux-mmc@vger.kernel.org - jirislaby@gmail.com - linux@arm.linux.org.uk - " linux-kernel@vger.kernel.org\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "Hi Jonas,\n" @@ -69,11 +64,11 @@ "> sources (requested without success).\n" "> \n" "> drivers/char/mxser.c drivers/char/mxser.h: MOXA\n" - "> SMARTIO/INDUSTIO/INTELLIO SERIAL CARD (Ji\305\231\303\255 Slab\303\275):\n" + "> SMARTIO/INDUSTIO/INTELLIO SERIAL CARD (Ji?? Slab?):\n" "> Force board setup for CONFIG_ARCH_MOXART.\n" "> ASYNCB_CLOSING is avoided because of a lockup (infinite wait after\n" "> tty_wait_until_sent). Why this happens is unknown (to me) I'm hoping\n" - "> someone (Ji\305\231\303\255?) can shed light. SysRq trace @ http://ideone.com/e845mr\n" + "> someone (Ji???) can shed light. SysRq trace @ http://ideone.com/e845mr\n" "> What significance does ASYNCB_CLOSING have?\n" "> Obviously, automatic detection is better but \"mxser_read_register\" is\n" "> pointless on this hardware. What to do instead? Is it better to make a\n" @@ -97,9 +92,9 @@ "> https://linux-2-6-34-14-moxart.googlecode.com/files/linux-2.6.34.14-moxart.patch\n" "> --\n" "> To unsubscribe from this list: send the line \"unsubscribe linux-kernel\" in\n" - "> the body of a message to majordomo@vger.kernel.org\n" + "> the body of a message to majordomo at vger.kernel.org\n" "> More majordomo info at http://vger.kernel.org/majordomo-info.html\n" "> Please read the FAQ at http://www.tux.org/lkml/\n" > -d686229f26394335509239b4b4d11b3548d57d75653e5f2fd1b0c073833805a2 +cc361ae96be3bb1491e1bd29ced3a7baa78539de853744a2aa73b4c46998fdc3
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.