diff for duplicates of <200904162110.05150.mb@bu3sch.de> diff --git a/a/1.txt b/N1/1.txt index 319b3de..2c905ce 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,42 +1,32 @@ On Thursday 16 April 2009 20:59:34 Johannes Berg wrote: -> On Thu, 2009-04-16 at 20:47 +0200, G=C3=A1bor Stefanik wrote: ->=20 +> On Thu, 2009-04-16 at 20:47 +0200, Gábor Stefanik wrote: +> > > Alternatively, the meanings of the {0,0} and {1,1} cases could be -> > switched around (making the {0,0} case more logical, at the expense= - of +> > switched around (making the {0,0} case more logical, at the expense of > > the {1,1} one): -> >=20 +> > > > TX Flags absent: Use RTS & CTS as needed. > > TX Flags present: { -> > RTS=3D0, CTS=3D0: Use RTS & CTS as needed. -> > RTS=3D0, CTS=3D1: Use CTS-to-self. -> > RTS=3D1, CTS=3D0: Use RTS/CTS-handshake. -> > RTS=3D1, CTS=3D1: Use neither RTS nor CTS. +> > RTS=0, CTS=0: Use RTS & CTS as needed. +> > RTS=0, CTS=1: Use CTS-to-self. +> > RTS=1, CTS=0: Use RTS/CTS-handshake. +> > RTS=1, CTS=1: Use neither RTS nor CTS. -The first and the last thing let my head explode, because it's not what= - somebody -would expect from such bits. This kind of logic is also used in wext. A= -nd it's why I hate wext. -"bit0 means x, bit1 means y, buuuuuuuuuuuuuuuut iff both bits are set t= -he whole logic +The first and the last thing let my head explode, because it's not what somebody +would expect from such bits. This kind of logic is also used in wext. And it's why I hate wext. +"bit0 means x, bit1 means y, buuuuuuuuuuuuuuuut iff both bits are set the whole logic is inverted and whatever..." -That complicates _every_ single test of the bit (always need if (bit0 i= -s set but not bit1)) -It produces spaghetti code interpreting these bits with lots of branche= -s and special +That complicates _every_ single test of the bit (always need if (bit0 is set but not bit1)) +It produces spaghetti code interpreting these bits with lots of branches and special conditions that nobody does understand by reading the code alone. -If you can't encode your functionality into a boolean, do _NOT_ use bit= -s to encode it. +If you can't encode your functionality into a boolean, do _NOT_ use bits to encode it. Use integers to encode tristate or quadstate or whatever. -You essentially _did_ that already, if you look at your bits. You use t= -he two individual bits -as 2bit integer value. So why not spell it out and use an integer field= - for that information? +You essentially _did_ that already, if you look at your bits. You use the two individual bits +as 2bit integer value. So why not spell it out and use an integer field for that information? ---=20 +-- Greetings, Michael. -- -To unsubscribe from this list: send the line "unsubscribe linux-wireles= -s" in -the body of a message to majordomo@vger.kernel.org +To unsubscribe from this list: send the line "unsubscribe linux-wireless" 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 8b88eda..ab38d32 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,56 +1,47 @@ "ref\069e28c910904141733m72ce521ap8f1865bec991fff7@mail.gmail.com\0" "ref\069e28c910904161147h5a68d3b5nd054b043d6ad2719@mail.gmail.com\0" "ref\01239908374.26575.20.camel@johannes.local\0" - "From\0Michael Buesch <mb@bu3sch.de>\0" + "ref\01239908374.26575.20.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org\0" + "From\0Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>\0" "Subject\0Re: [Proposal]TX flags\0" "Date\0Thu, 16 Apr 2009 21:10:04 +0200\0" - "To\0Johannes Berg <johannes@sipsolutions.net>\0" - "Cc\0G\303\241bor Stefanik <netrolller.3d@gmail.com>" - radiotap@radiotap.org - " linux-wireless <linux-wireless@vger.kernel.org>\0" + "To\0Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>\0" + "Cc\0G\303\241bor Stefanik <netrolller.3d-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>" + radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org + " linux-wireless <linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>\0" "\00:1\0" "b\0" "On Thursday 16 April 2009 20:59:34 Johannes Berg wrote:\n" - "> On Thu, 2009-04-16 at 20:47 +0200, G=C3=A1bor Stefanik wrote:\n" - ">=20\n" + "> On Thu, 2009-04-16 at 20:47 +0200, G\303\241bor Stefanik wrote:\n" + "> \n" "> > Alternatively, the meanings of the {0,0} and {1,1} cases could be\n" - "> > switched around (making the {0,0} case more logical, at the expense=\n" - " of\n" + "> > switched around (making the {0,0} case more logical, at the expense of\n" "> > the {1,1} one):\n" - "> >=20\n" + "> > \n" "> > TX Flags absent: Use RTS & CTS as needed.\n" "> > TX Flags present: {\n" - "> > RTS=3D0, CTS=3D0: Use RTS & CTS as needed.\n" - "> > RTS=3D0, CTS=3D1: Use CTS-to-self.\n" - "> > RTS=3D1, CTS=3D0: Use RTS/CTS-handshake.\n" - "> > RTS=3D1, CTS=3D1: Use neither RTS nor CTS.\n" + "> > RTS=0, CTS=0: Use RTS & CTS as needed.\n" + "> > RTS=0, CTS=1: Use CTS-to-self.\n" + "> > RTS=1, CTS=0: Use RTS/CTS-handshake.\n" + "> > RTS=1, CTS=1: Use neither RTS nor CTS.\n" "\n" - "The first and the last thing let my head explode, because it's not what=\n" - " somebody\n" - "would expect from such bits. This kind of logic is also used in wext. A=\n" - "nd it's why I hate wext.\n" - "\"bit0 means x, bit1 means y, buuuuuuuuuuuuuuuut iff both bits are set t=\n" - "he whole logic\n" + "The first and the last thing let my head explode, because it's not what somebody\n" + "would expect from such bits. This kind of logic is also used in wext. And it's why I hate wext.\n" + "\"bit0 means x, bit1 means y, buuuuuuuuuuuuuuuut iff both bits are set the whole logic\n" "is inverted and whatever...\"\n" - "That complicates _every_ single test of the bit (always need if (bit0 i=\n" - "s set but not bit1))\n" - "It produces spaghetti code interpreting these bits with lots of branche=\n" - "s and special\n" + "That complicates _every_ single test of the bit (always need if (bit0 is set but not bit1))\n" + "It produces spaghetti code interpreting these bits with lots of branches and special\n" "conditions that nobody does understand by reading the code alone.\n" - "If you can't encode your functionality into a boolean, do _NOT_ use bit=\n" - "s to encode it.\n" + "If you can't encode your functionality into a boolean, do _NOT_ use bits to encode it.\n" "Use integers to encode tristate or quadstate or whatever.\n" - "You essentially _did_ that already, if you look at your bits. You use t=\n" - "he two individual bits\n" - "as 2bit integer value. So why not spell it out and use an integer field=\n" - " for that information?\n" + "You essentially _did_ that already, if you look at your bits. You use the two individual bits\n" + "as 2bit integer value. So why not spell it out and use an integer field for that information?\n" "\n" - "--=20\n" + "-- \n" "Greetings, Michael.\n" "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-wireles=\n" - "s\" in\n" - "the body of a message to majordomo@vger.kernel.org\n" + "To unsubscribe from this list: send the line \"unsubscribe linux-wireless\" 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 -149b90cfa5a0cc1639ee99caf6d6527b57a194e29a7a1a32ab3c07e86360435f +c5d06a6586b699547fd687cdc3314b0a113b0186ec99659ff796848d708a692a
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.