Subject: Re: [linux-lvm] Re: [repost] Announce: Linux-OpenLVM mailing list
To: lewis@sistina.com (AJ Lewis)
Date: Thu, 19 Apr 2001 21:03:24 +0100 (BST)
Cc: linux-lvm@sistina.com, alan@lxorguk.ukuu.org.uk (Alan Cox),
        jes@linuxcare.com (Jes Sorensen), linux-kernel@vger.kernel.org,
        linux-openlvm@nl.linux.org, arjanv@redhat.com (Arjan van de Ven),
        axboe@suse.de (Jens Axboe), mkp@linuxcare.com (Martin Kasper Petersen),
        riel@conectiva.com.br
In-Reply-To: <20010419145337.K10345@sistina.com> from "AJ Lewis" at Apr 19, 2001 02:53:37 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <E14qKeF-0007wb-00@the-village.bc.nu>
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Sender: linux-kernel-owner@vger.kernel.org

> As far as getting patches into the stock kernel, we've been sending patches
> to Linus for over a month now, and none of them have made it in.  Maybe
> someone has some pointers on how we get our code past his filters.

Has it occured to you that some of this might be because the code does stuff
like hide flags in the low bits of addresses and do unchecked kmallocs ?
Things people have tried to send patches for ..

The best way to get stuff to Linus is to feed him changes one at a time and
make them all clean and clearly correct. When I have a big set of changes I
normally start by feeding Linus all the 'fluff' - spelling checks and small
warning fixes. After that its normally easy to pick out changes one at a time
and feed them on.

Given 500 lines of mixed up diff it is very hard to verify the correctness of
anything. 

Alan

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