| To: | Linux XFS <linux-xfs@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: Preemptive kernel patch on top of XFS |
| From: | Sean Neakums <sneakums@xxxxxxxx> |
| Date: | Thu, 27 Dec 2001 01:00:10 +0000 |
| In-reply-to: | <1009412017.20092.3.camel@Liberator> (Eric Sandeen's message of "26 Dec 2001 18:13:36 -0600") |
| Mail-followup-to: | Linux XFS <linux-xfs@xxxxxxxxxxx> |
| References: | <Pine.LNX.4.33.0112261635360.6274-100000@thulcandra.chpc.utah.edu> <1009412017.20092.3.camel@Liberator> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.1 (i386-debian-linux-gnu) |
begin Eric Sandeen quotation: > On Wed, 2001-12-26 at 17:36, drr@xxxxxxxxxxxxx wrote: >> On Wed, 26 Dec 2001, Alp ATICI wrote: >> >> > Which patch should we apply to the kernel first? >> My general rule is to apply bigger, more intrusive patches first, so I do >> XFS before preemption. >> > I did it this way (XFS first) and I don't recall any problems. If > there was a merge conflict, it was trivial to resolve. The preempt patch has been applying cleanly to SGI's CVS tree for me since I started using it, round about the .15 pre-patches. It works great, too. -- ///////////////// | | The spark of a pin <sneakums@xxxxxxxx> | (require 'gnu) | dropping, falling feather-like. \\\\\\\\\\\\\\\\\ | | There is too much noise. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Preemptive kernel patch on top of XFS, Eric Sandeen |
|---|---|
| Next by Date: | Re: CML2, Keith Owens |
| Previous by Thread: | Re: Preemptive kernel patch on top of XFS, Eric Sandeen |
| Next by Thread: | Problem getting snapshots mounted for ext3 & resierfs on 2.4.17-xfs+lvm-1.0.1, Adrian Head |
| Indexes: | [Date] [Thread] [Top] [All Lists] |