diff for duplicates of <d120d50005042509326241a302@mail.gmail.com> diff --git a/a/1.txt b/N1/1.txt index 7ba56e6..5ad6660 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -10,7 +10,7 @@ On 4/25/05, Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote: > I think there might be only 2 "must have" methods - read and write. > I plan to implement them using connector, so probably they will go away > completely. -.. +... > > You will not be able to cram all 1-wire devices into unified > > interface. You will need to build classes on top of it and you might > > use connector (I am not sure) bit not on w1 bus level. @@ -42,7 +42,7 @@ interface tfor a class. And class does not have to be confined to a signe bus, it can span across several buses, providing unified interface to a group of similar objects. -.. +... > If I understand you correctly, "lifetime rules" are implemented in a > following way: > when object is created it has 0 refcnt, each access increments it and @@ -244,7 +244,7 @@ a thread goes mad maybe it's a good thing that it can be killed. > What you do is exactly the same that already exist, but using other > model. > No need to dig into device model in a such way. -.. +... > the problem is that device model[which is not the main part of the w1 > system] > is interfere to the existing locking schema [which is quite big and diff --git a/a/content_digest b/N1/content_digest index 018f57f..ba29658 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,9 +2,9 @@ "ref\01114089504.29655.93.camel@uganda\0" "ref\0d120d50005042107314cbacdea@mail.gmail.com\0" "ref\01114420131.8527.52.camel@uganda\0" - "From\0dmitry.torokhov@gmail.com (Dmitry Torokhov)\0" - "Subject\0[RFC/PATCH 0/22] W1: sysfs, lifetime and other fixes\0" - "Date\0Thu, 19 May 2005 06:25:54 +0000\0" + "From\0Dmitry Torokhov <dmitry.torokhov@gmail.com>\0" + "Subject\0Re: [RFC/PATCH 0/22] W1: sysfs, lifetime and other fixes\0" + "Date\0Mon, 25 Apr 2005 11:32:14 -0500\0" "To\0johnpol@2ka.mipt.ru\0" "Cc\0sensors@stimpy.netroedge.com" LKML <linux-kernel@vger.kernel.org> @@ -23,7 +23,7 @@ "> I think there might be only 2 \"must have\" methods - read and write.\n" "> I plan to implement them using connector, so probably they will go away\n" "> completely.\n" - "..\n" + "...\n" "> > You will not be able to cram all 1-wire devices into unified\n" "> > interface. You will need to build classes on top of it and you might\n" "> > use connector (I am not sure) bit not on w1 bus level.\n" @@ -55,7 +55,7 @@ "signe bus, it can span across several buses, providing unified\n" "interface to a group of similar objects.\n" "\n" - ".. \n" + "... \n" "> If I understand you correctly, \"lifetime rules\" are implemented in a\n" "> following way:\n" "> when object is created it has 0 refcnt, each access increments it and\n" @@ -257,7 +257,7 @@ "> What you do is exactly the same that already exist, but using other\n" "> model.\n" "> No need to dig into device model in a such way.\n" - "..\n" + "...\n" "> the problem is that device model[which is not the main part of the w1\n" "> system]\n" "> is interfere to the existing locking schema [which is quite big and\n" @@ -307,4 +307,4 @@ "-- \n" Dmitry -5aac74e232979b272ab82b11607f5e442119ada3b119b8b160bcea7aa3fae5a7 +c7f2a197e7b34857e7a355380a10305fbd1006aae223e4fb80c1cd7479f5fb36
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.