lkcd
[Top] [All Lists]

Re: FW: drivers/block/dump.c fixes

To: bharata@xxxxxxxxxx
Subject: Re: FW: drivers/block/dump.c fixes
From: "Matt D. Robinson" <yakker@xxxxxxxxxxxxxx>
Date: Mon, 24 Sep 2001 23:51:37 -0700
Cc: lkcd@xxxxxxxxxxx
Organization: Alacritech, Inc.
References: <Pine.LNX.4.30.0109240020380.14832-100000@xxxxxxxxxxxxxxxxxxxx> <3BAF71D6.E4CD82E@xxxxxxxxxxxxxx> <20010925112511.A25747@xxxxxxxxxx>
Sender: owner-lkcd@xxxxxxxxxxx
Bharata B Rao wrote:
> 
> On Mon, Sep 24, 2001 at 10:48:06AM -0700, Matt D. Robinson wrote:
> > > Hmmm, hopefully we didn't step on each other, I just checked
> > > fixes to both of these 5 minutes ago. :)
> > >
> > > I'll look at the logs.
> > >
> > > |>Regards,
> > > |>Bharata.
> > > |>> --Matt
> >
> 
> Corrected the overlaps in checkins of driver/dump/dump_base.c (originally
> drivers/block/dump.c).
> Also updated drivers/dump/dump_i386.c to conform __dump_silence_system() to
> the new logic of silencing/resuming in stages.

Any problems with the new driver layout/builds so far?  I haven't
encountered any (yet).

The tree looks somewhat sane for once. :)

--Matt

> Regards,
> Bharata.
> 
> > Looks like most of the tree moves/updates are done.  For those
> > of you working directly out of the CVS tree, you're going to need
> > to back-out any changes related to the previous tree (that includes
> > all modifications in arch/*/kernel, etc.) and then update with all
> > the new files.
> >
> > There's now a drivers/dump directory (drivers/block/dump.c is
> > no longer pertinent, everything is being built in its own
> > directory) where everything now resides.
> >
> > 4.0 is pending now a couple more crash tests.
> >
> > --Matt

<Prev in Thread] Current Thread [Next in Thread>