public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: AJ Lewis <lewis@sistina.com>,
	linux-lvm@sistina.com, Jes Sorensen <jes@linuxcare.com>,
	linux-kernel@vger.kernel.org, linux-openlvm@nl.linux.org,
	Arjan van de Ven <arjanv@redhat.com>, Jens Axboe <axboe@suse.de>,
	Martin Kasper Petersen <mkp@linuxcare.com>,
	riel@conectiva.com.br
Subject: Re: [linux-lvm] Re: [repost] Announce: Linux-OpenLVM mailing list
Date: Thu, 19 Apr 2001 14:52:59 -0700	[thread overview]
Message-ID: <3ADF5E3B.6070309@megapathdsl.net> (raw)
In-Reply-To: <E14qKeF-0007wb-00@the-village.bc.nu>

Alan Cox wrote:

>>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. 


The IrDA folks have had a similar struggle.  AJ, perhaps it would be
helpful for you to read the discussion that took place regarding getting
a bunch of IrDA code merged into the 2.4 tree:

http://www.pasta.cs.uit.no/pipermail/linux-irda/2000-November/001923.html

Dag Brattli <dagb@fast.no> eventually had a discussion with Linus and
hashed out what he needed to do to get Linus to accept his big patch. 
It all
worked out very well, IIRC.

	Miles


  reply	other threads:[~2001-04-19 21:53 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-19 17:51 [repost] Announce: Linux-OpenLVM mailing list Jes Sorensen
2001-04-19 18:29 ` AJ Lewis
2001-04-19 18:34   ` Jeff Garzik
2001-04-19 18:35   ` Rik van Riel
2001-04-24 14:58     ` Heinz J. Mauelshagen
2001-04-19 18:48   ` Jens Axboe
2001-04-24 14:54     ` Heinz J. Mauelshagen
2001-04-19 19:02   ` Alan Cox
2001-04-19 19:24     ` AJ Lewis
2001-04-19 19:33       ` Jens Axboe
2001-04-19 19:46         ` Martin K. Petersen
2001-04-24 15:00           ` Heinz J. Mauelshagen
2001-04-19 19:35       ` Jes Sorensen
2001-04-19 19:44         ` AJ Lewis
2001-04-19 19:45       ` [linux-lvm] " Andreas Dilger
2001-04-19 19:51         ` Alan Cox
2001-04-19 19:53         ` Rik van Riel
2001-04-19 19:53         ` AJ Lewis
2001-04-19 19:56           ` Jens Axboe
2001-04-19 20:03           ` Alan Cox
2001-04-19 21:52             ` Miles Lane [this message]
2001-04-19 20:09           ` Jeff Garzik
2001-04-19 20:16             ` AJ Lewis
2001-04-20 10:34             ` Patrick Caulfield
2001-04-20  0:41           ` Andreas Dilger
2001-04-19 19:55         ` Christoph Hellwig
2001-04-20  1:29         ` Paul Jakma
2001-04-19 20:33       ` Miles Lane
2001-04-20 12:36         ` Doug McNaught
2001-04-20 22:55           ` Matti Aarnio
2001-04-21 20:45             ` Rik van Riel
2001-04-19 19:17   ` Jes Sorensen
2001-04-19 19:26     ` AJ Lewis
2001-04-19 19:40       ` Jes Sorensen
2001-04-19 19:19   ` Martin K. Petersen
2001-04-19 19:40   ` [linux-lvm] " AJ Lewis
2001-04-19 19:49     ` Alan Cox
2001-04-19 21:25     ` Kurt Garloff
  -- strict thread matches above, loose matches on Subject: below --
2001-04-20  7:37 Luca Berra
2001-04-20  7:59 ` Jeff Garzik
     [not found] <20010419144815.J10345@sistina.com>
2001-04-20 19:24 ` Heinz J. Mauelshagen
2001-04-20 17:39   ` [linux-lvm] " Wichert Akkerman

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=3ADF5E3B.6070309@megapathdsl.net \
    --to=miles@megapathdsl.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjanv@redhat.com \
    --cc=axboe@suse.de \
    --cc=jes@linuxcare.com \
    --cc=lewis@sistina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-lvm@sistina.com \
    --cc=linux-openlvm@nl.linux.org \
    --cc=mkp@linuxcare.com \
    --cc=riel@conectiva.com.br \
    /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