diff for duplicates of <20150113170007.GV1386@lahna.fi.intel.com> diff --git a/a/1.txt b/N1/1.txt index 0fd48e3..6c7be02 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -9,8 +9,8 @@ On Tue, Jan 13, 2015 at 05:48:29PM +0100, Wolfram Sang wrote: > > > > Instead of doing that we assign the first address to the device and then > > > > let the driver handle rest of the addresses as it wishes. > > > > -> > > > Signed-off-by: Mika Westerberg <mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> -> > > > Cc: Srinivas Pandruvada <srinivas.pandruvada-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> +> > > > Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com> +> > > > Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> > > > > > > Yes, seems better than what we do know. But maybe taking the lowest > > > address is a bit better heuristic than taking the first address? diff --git a/a/content_digest b/N1/content_digest index bd71e29..2fa39e5 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,13 +2,13 @@ "ref\020150113155059.GN7660@katana\0" "ref\01421167477.4459.229.camel@spandruv-desktop.jf.intel.com\0" "ref\020150113164829.GO7660@katana\0" - "From\0Mika Westerberg <mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>\0" + "From\0Mika Westerberg <mika.westerberg@linux.intel.com>\0" "Subject\0Re: [PATCH] i2c / ACPI: Pick the first address if device has multiple\0" "Date\0Tue, 13 Jan 2015 19:00:07 +0200\0" - "To\0Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>\0" - "Cc\0Srinivas Pandruvada <srinivas.pandruvada-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>" - linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org - " linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\0" + "To\0Wolfram Sang <wsa@the-dreams.de>\0" + "Cc\0Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>" + linux-i2c@vger.kernel.org + " linux-kernel@vger.kernel.org\0" "\00:1\0" "b\0" "On Tue, Jan 13, 2015 at 05:48:29PM +0100, Wolfram Sang wrote:\n" @@ -22,8 +22,8 @@ "> > > > Instead of doing that we assign the first address to the device and then\n" "> > > > let the driver handle rest of the addresses as it wishes.\n" "> > > > \n" - "> > > > Signed-off-by: Mika Westerberg <mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>\n" - "> > > > Cc: Srinivas Pandruvada <srinivas.pandruvada-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>\n" + "> > > > Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>\n" + "> > > > Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>\n" "> > > \n" "> > > Yes, seems better than what we do know. But maybe taking the lowest\n" "> > > address is a bit better heuristic than taking the first address?\n" @@ -41,4 +41,4 @@ "\n" Also I think it is more consistent that way. -3904b636b83c5439f3bf7f0808106a22c4ec6538f98c5fe9830290e6e7d936af +c47b3303691236c78c6060841d953b3fc40c4eb01fcc3cc564903312a2f7eb9f
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.