diff for duplicates of <201104211612.49805.arnd@arndb.de> diff --git a/a/1.txt b/N1/1.txt index 22a050a..7f73792 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,7 +1,7 @@ On Wednesday 20 April 2011, Arend van Spriel wrote: > The open-source community is looking for a library which will detect > cores in a chip using axi backplane. Another proposal has been -> sent by Rafał Miłecki, which registers detected cores in the linux +> sent by Rafa? Mi?ecki, which registers detected cores in the linux > device tree to be claimed by device drivers. This implies cores will > always provide a system function to the kernel which is indepent from > other cores and have very loose or no coupling. If this is not true, @@ -51,7 +51,7 @@ the differences internally? This list to me is a strong hint that the cores behind the AXI bridge should normally be actual devices in Linux, i.e. the approach that -Rafał suggested. The vast majority of these is something that in Linux +Rafa? suggested. The vast majority of these is something that in Linux would be operated by a device driver. The exceptions that I can see are CPU cores and bus bridges, both of which we typically also represent as devices in the flattened device tree, even though they typically diff --git a/a/content_digest b/N1/content_digest index ba498fa..2a0ba5b 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,27 +1,14 @@ "ref\01303331669-31293-1-git-send-email-arend@broadcom.com\0" - "From\0Arnd Bergmann <arnd@arndb.de>\0" - "Subject\0Re: [PATCH] drivers: brcmaxi: provide amba axi functionality in separate module\0" + "From\0arnd@arndb.de (Arnd Bergmann)\0" + "Subject\0[PATCH] drivers: brcmaxi: provide amba axi functionality in separate module\0" "Date\0Thu, 21 Apr 2011 16:12:49 +0200\0" - "To\0Arend van Spriel <arend@broadcom.com>\0" - "Cc\0zajec5@gmail.com" - linux-kernel@vger.kernel.org - linux-wireless@vger.kernel.org - linux-arm-kernel@lists.infradead.org - b43-dev@lists.infradead.org - George Kashperko <george@znau.edu.ua> - Jonas Gorski <jonas.gorski@gmail.com> - Hauke Mehrtens <hauke@hauke-m.de> - Russell King <rmk@arm.linux.org.uk> - Larry Finger <Larry.Finger@lwfinger.net> - Andy Botting <andy@andybotting.com> - Greg KH <greg@kroah.com> - " Michael Buesch <m@bues.ch>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On Wednesday 20 April 2011, Arend van Spriel wrote:\n" "> The open-source community is looking for a library which will detect\n" "> cores in a chip using axi backplane. Another proposal has been\n" - "> sent by Rafa\305\202 Mi\305\202ecki, which registers detected cores in the linux\n" + "> sent by Rafa? Mi?ecki, which registers detected cores in the linux\n" "> device tree to be claimed by device drivers. This implies cores will\n" "> always provide a system function to the kernel which is indepent from\n" "> other cores and have very loose or no coupling. If this is not true,\n" @@ -71,7 +58,7 @@ "\n" "This list to me is a strong hint that the cores behind the AXI bridge\n" "should normally be actual devices in Linux, i.e. the approach that\n" - "Rafa\305\202 suggested. The vast majority of these is something that in Linux\n" + "Rafa? suggested. The vast majority of these is something that in Linux\n" "would be operated by a device driver. The exceptions that I can see\n" "are CPU cores and bus bridges, both of which we typically also represent\n" "as devices in the flattened device tree, even though they typically\n" @@ -79,4 +66,4 @@ "\n" "\tArnd" -fe3454752e2e52fdd280fad7bdcf897805ef302857bfe72709877d14dced5897 +f9305ed20cbbe26d47903d2c4a09485da0a8bdea7139911b1da368dc8999aef1
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.