On Friday, January 30, 2009 1:21 am Andrew Morton wrote:
> On Fri, 30 Jan 2009 10:13:55 +0100 Thomas Hellstr__m
wrote:
> > >> Sounds right to me. The offsets are just handles, not real file
> > >> objects or backing store addresses. We use them to take advantage of
> > >> all the inode address
Andrew Morton wrote:
> On Fri, 30 Jan 2009 10:13:55 +0100 Thomas Hellstr__m
> wrote:
>
>
Sounds right to me. The offsets are just handles, not real file objects
or
backing store addresses. We use them to take advantage of all the inode
address mapping helpers, since th
On Fri, 30 Jan 2009 10:13:55 +0100 Thomas Hellstr__m
wrote:
> >> Sounds right to me. The offsets are just handles, not real file objects
> >> or
> >> backing store addresses. We use them to take advantage of all the inode
> >> address mapping helpers, since they track stuff for us.
> >>
> >
Andrew Morton wrote:
> On Thu, 29 Jan 2009 19:50:17 -0800 Jesse Barnes
> wrote:
>
>
>> On Thursday, January 29, 2009 5:43 pm Dave Airlie wrote:
>>
>>> On Fri, Jan 30, 2009 at 11:20 AM, Andrew Morton
>>>
hm, I'm a bit surprised to see the drm code using `struct
address_spa
On Fri, Jan 30, 2009 at 05:44, Andrew Morton wrote:
> On Thu, 29 Jan 2009 19:50:17 -0800 Jesse Barnes
> wrote:
>
>> On Thursday, January 29, 2009 5:43 pm Dave Airlie wrote:
>> > On Fri, Jan 30, 2009 at 11:20 AM, Andrew Morton
>> > > hm, I'm a bit surprised to see the drm code using `struct
>> >
On Thu, 29 Jan 2009 19:50:17 -0800 Jesse Barnes
wrote:
> On Thursday, January 29, 2009 5:43 pm Dave Airlie wrote:
> > On Fri, Jan 30, 2009 at 11:20 AM, Andrew Morton
> > > hm, I'm a bit surprised to see the drm code using `struct
> > > address_space' and read_mapping_page() and unmap_mapping_ran
On Thursday, January 29, 2009 5:43 pm Dave Airlie wrote:
> On Fri, Jan 30, 2009 at 11:20 AM, Andrew Morton
> > hm, I'm a bit surprised to see the drm code using `struct
> > address_space' and read_mapping_page() and unmap_mapping_range() and
> > such. I thought those only worked with regular files
On Fri, Jan 30, 2009 at 11:20 AM, Andrew Morton
wrote:
> On Fri, 30 Jan 2009 11:06:47 +1000 Dave Airlie wrote:
>
>> On Fri, Jan 30, 2009 at 10:30 AM, Andrew Morton
>> wrote:
>> > (cc's added)
>> >
>> > On Wed, 21 Jan 2009 13:27:48 +0100
>> > Sami Kerola wrote:
>> >
>> >> I compiled the Torvalds
On Fri, 30 Jan 2009 11:06:47 +1000 Dave Airlie wrote:
> On Fri, Jan 30, 2009 at 10:30 AM, Andrew Morton
> wrote:
> > (cc's added)
> >
> > On Wed, 21 Jan 2009 13:27:48 +0100
> > Sami Kerola wrote:
> >
> >> I compiled the Torvalds git kernel 2.6.29-rc2-00013 and I got an oops.
> >> The oops happe
On Thu, Jan 29, 2009 at 5:06 PM, Dave Airlie wrote:
> On Fri, Jan 30, 2009 at 10:30 AM, Andrew Morton
> wrote:
>> (cc's added)
>>
>> On Wed, 21 Jan 2009 13:27:48 +0100
>> Sami Kerola wrote:
>>
>>> I compiled the Torvalds git kernel 2.6.29-rc2-00013 and I got an oops.
>>> The oops happens when ev
On Fri, Jan 30, 2009 at 10:30 AM, Andrew Morton
wrote:
> (cc's added)
>
> On Wed, 21 Jan 2009 13:27:48 +0100
> Sami Kerola wrote:
>
>> I compiled the Torvalds git kernel 2.6.29-rc2-00013 and I got an oops.
>> The oops happens when ever X starts. Initially I was booting with run
>> level 5 and it
(cc's added)
On Wed, 21 Jan 2009 13:27:48 +0100
Sami Kerola wrote:
> I compiled the Torvalds git kernel 2.6.29-rc2-00013 and I got an oops.
> The oops happens when ever X starts. Initially I was booting with run
> level 5 and it hung. I tried to use run level to 3 and an operating
> system start
12 matches
Mail list logo
