mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthias Andree <matthias.andree@gmx.de>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>,
	"Theodore Ts'o" <tytso@valinux.com>
Subject: Re: FAIL: 2.2.18 + AA-VM-global-7 + serial 5.05
Date: Fri, 22 Dec 2000 17:35:38 +0100	[thread overview]
Message-ID: <20001222173538.A12949@krusty.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <20001222154757.A1167@emma1.emma.line.org> <20001222162159.A29397@athlon.random>
In-Reply-To: <20001222162159.A29397@athlon.random>; from andrea@suse.de on Fri, Dec 22, 2000 at 16:21:59 +0100

Andrea Arcangeli schrieb am Freitag, den 22. Dezember 2000:

> On Fri, Dec 22, 2000 at 03:47:57PM +0100, Matthias Andree wrote:
> > I suspect that these patches are mutually incompatible.
> 
> did you checked that there are no rejects after patching :)

Yes, I did, there were none.

I had one patch that required a fuzz factor, but it only has a vendor ID
definition in pci.h. It's the patch by Lukasz Trabinski, Subject "Re:
[patch] 2.2.18 PCI_DEVICE_ID_OXSEMI_16PCI954", Date 2000-12-16 19:51
EST, Archive at
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0012.2/0126.html

That patch has been approved by Theodore Y Tso as being correct.

The other patches I applied did not leave any rejects behind.

> > Could somebody please have a look at this? I will test or provide more
> > information as requested.
> 
> Where's serial 5.05 so I can have a look?

It's at http://sourceforge.net/projects/serial/ and since these are down
ATM, I'm keeping a copy at
http://www-dt.e-technik.uni-dortmund.de/~ma/kernelpatches/v2.2/v2.2.18/

Procedure:

1. fetch 2.2.18-fix-serial-5.05-pre.patch (has also been posted here, it
   just adds a missing #define to pci.h)
2. fetch serial-5.05.tar.gz
3. patch the kernel with that 2.2.18-fix-serial-5.05-pre.patch, it takes
   a high fuzz factor (try patch -p1 -F10)
4. unpack serial-5.05
5. sh install-in-kernel
6. patch with VM-global-2.2.18pre25-7
7. make clean dep bzImage modules, install, boot, and see it hang.

Note my kernel also contains the IDE and I²C patches, should that
matter, if it matters, please tell the corresponding maintainer there's
an incompatibility.

For what it's worth, that www-dt server directory also has my config,
it's named config-ma2.

-- 
Matthias Andree



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-22 17:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-22 14:47 Matthias Andree
2000-12-22 15:21 ` Andrea Arcangeli
2000-12-22 16:35   ` Matthias Andree [this message]
2000-12-22 16:59     ` Stuart MacDonald
2000-12-22 17:13       ` Matthias Andree
2001-01-02  2:00 ` [PATCH] " Chip Salzenberg
2001-01-22  2:53   ` Resolved: " Matthias Andree

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20001222173538.A12949@krusty.e-technik.uni-dortmund.de \
    --to=matthias.andree@gmx.de \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@valinux.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®