diff for duplicates of <200901022028.32764.mb@bu3sch.de> diff --git a/a/1.txt b/N1/1.txt index 831c34d..5c5ad36 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,30 +1,40 @@ -On Friday 02 January 2009 19:59:15 Stefanik G?bor wrote: +On Friday 02 January 2009 19:59:15 Stefanik G=E1bor wrote: > On Fri, Jan 2, 2009 at 7:56 PM, Michael Buesch <mb@bu3sch.de> wrote: -> > On Friday 02 January 2009 19:52:49 Stefanik G?bor wrote: +> > On Friday 02 January 2009 19:52:49 Stefanik G=E1bor wrote: > >> On Fri, Jan 2, 2009 at 11:05 AM, Vasanthakumar Thiagarajan > >> <vasanth@atheros.com> wrote: > >> > Signed-off-by: Vasanthakumar Thiagarajan <vasanth@atheros.com> > >> > --- > >> > drivers/net/wireless/ath9k/ath9k.h | 5 +++++ -> >> > drivers/net/wireless/ath9k/hw.c | 33 +++++++++++++++++++++++++++++++++ +> >> > drivers/net/wireless/ath9k/hw.c | 33 +++++++++++++++++++++= +++++++++++++ > >> > drivers/net/wireless/ath9k/main.c | 9 +++++++-- > >> > drivers/net/wireless/ath9k/reg.h | 10 ++++++++++ > >> > 4 files changed, 55 insertions(+), 2 deletions(-) > >> > > >> > <snip> > >> -> >> Probably a NOBTCOEX modparam might be a good idea - when implementing +> >> Probably a NOBTCOEX modparam might be a good idea - when implement= +ing > >> BT coexistence in b43, a lot of non-BT-aware cards failed to work > > -> > And what makes you think that atheros also ships cards with broken btcoex support? -> +> > And what makes you think that atheros also ships cards with broken = +btcoex support? +>=20 > We can never know what vendors will do Well, I'd say that applies to any feature. Should we add modparams for all new features from now on? -I'd say we simply apply this patch and see what happens. Most likely nothing, -because the btcoex implementation in the atheros hardware works differently anyway. +I'd say we simply apply this patch and see what happens. Most likely no= +thing, +because the btcoex implementation in the atheros hardware works differe= +ntly anyway. --- +--=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 +More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 5ac602b..ce429f0 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,40 +2,56 @@ "ref\0200901021956.21785.mb@bu3sch.de\0" "ref\069e28c910901021059q5bc604afn62117fcdf937d813@mail.gmail.com\0" "From\0Michael Buesch <mb@bu3sch.de>\0" - "Subject\0[ath9k-devel] [PATCH] ath9k: Enable Bluetooth Coexistence support\0" + "Subject\0Re: [PATCH] ath9k: Enable Bluetooth Coexistence support\0" "Date\0Fri, 2 Jan 2009 20:28:32 +0100\0" - "To\0ath9k-devel@lists.ath9k.org\0" + "To\0Stefanik G\303\241bor <netrolller.3d@gmail.com>\0" + "Cc\0Vasanthakumar Thiagarajan <vasanth@atheros.com>" + linville@tuxdriver.com + linux-wireless@vger.kernel.org + Luis.Rodriguez@atheros.com + Jouni.Malinen@atheros.com + " ath9k-devel@lists.ath9k.org\0" "\00:1\0" "b\0" - "On Friday 02 January 2009 19:59:15 Stefanik G?bor wrote:\n" + "On Friday 02 January 2009 19:59:15 Stefanik G=E1bor wrote:\n" "> On Fri, Jan 2, 2009 at 7:56 PM, Michael Buesch <mb@bu3sch.de> wrote:\n" - "> > On Friday 02 January 2009 19:52:49 Stefanik G?bor wrote:\n" + "> > On Friday 02 January 2009 19:52:49 Stefanik G=E1bor wrote:\n" "> >> On Fri, Jan 2, 2009 at 11:05 AM, Vasanthakumar Thiagarajan\n" "> >> <vasanth@atheros.com> wrote:\n" "> >> > Signed-off-by: Vasanthakumar Thiagarajan <vasanth@atheros.com>\n" "> >> > ---\n" "> >> > drivers/net/wireless/ath9k/ath9k.h | 5 +++++\n" - "> >> > drivers/net/wireless/ath9k/hw.c | 33 +++++++++++++++++++++++++++++++++\n" + "> >> > drivers/net/wireless/ath9k/hw.c | 33 +++++++++++++++++++++=\n" + "++++++++++++\n" "> >> > drivers/net/wireless/ath9k/main.c | 9 +++++++--\n" "> >> > drivers/net/wireless/ath9k/reg.h | 10 ++++++++++\n" "> >> > 4 files changed, 55 insertions(+), 2 deletions(-)\n" "> >> >\n" "> >> > <snip>\n" "> >>\n" - "> >> Probably a NOBTCOEX modparam might be a good idea - when implementing\n" + "> >> Probably a NOBTCOEX modparam might be a good idea - when implement=\n" + "ing\n" "> >> BT coexistence in b43, a lot of non-BT-aware cards failed to work\n" "> >\n" - "> > And what makes you think that atheros also ships cards with broken btcoex support?\n" - "> \n" + "> > And what makes you think that atheros also ships cards with broken =\n" + "btcoex support?\n" + ">=20\n" "> We can never know what vendors will do\n" "\n" "Well, I'd say that applies to any feature.\n" "Should we add modparams for all new features from now on?\n" "\n" - "I'd say we simply apply this patch and see what happens. Most likely nothing,\n" - "because the btcoex implementation in the atheros hardware works differently anyway.\n" + "I'd say we simply apply this patch and see what happens. Most likely no=\n" + "thing,\n" + "because the btcoex implementation in the atheros hardware works differe=\n" + "ntly anyway.\n" "\n" - "-- \n" - Greetings, Michael. + "--=20\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" + More majordomo info at http://vger.kernel.org/majordomo-info.html -e7581cf5621281b8987e5c4b89bdfb957678190be70d0c24c27e17daba772364 +8dfa67eb582542fea945994bc892edab7d76e77413ff2d786d169b94359f0759
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.