Date: Wed, 2 Feb 2005 16:29:12 -0800
From: "David S. Miller" <davem@davemloft.net>
To: Fruhwirth Clemens <clemens@endorphin.org>
Cc: jmorris@redhat.com, akpm@osdl.org, linux-kernel@vger.kernel.org,
       michal@logix.cz, dm-crypt@saout.de
Subject: Re: [PATCH 01/04] Adding cipher mode context information to
 crypto_tfm
Message-Id: <20050202162912.2faa9f3a.davem@davemloft.net>
In-Reply-To: <1107390095.19339.26.camel@ghanima>
References: <Xine.LNX.4.44.0502021728140.5000-100000@thoron.boston.redhat.com>
	<1107386909.19339.9.camel@ghanima>
	<20050202153449.1e92c29a.davem@davemloft.net>
	<1107390095.19339.26.camel@ghanima>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1288
Lines: 32

On Thu, 03 Feb 2005 01:21:35 +0100
Fruhwirth Clemens <clemens@endorphin.org> wrote:

> I'm afraid, I'm not going to change it. I already lost too much time
> pushing LRW into the kernel.

The work has to be done by somebody.  Linus would certainly reject any
attempt I would make to push code with that kind of variable naming
in it.  So instead of blindly going:

1) dave try push to linus
2) linus says fix horrible variable studlyCaps names
3) dave asks patch submitter to fix
4) submitter submits new patch
5) dave retries pushing to linus

I'm reducing it to one step, by asking that it be done now, thus
saving a lot of wasted time on everyone's part.

Submitting your first major patch or set of changes can be incredibly
frustrating.  It took more than a year before people like Linus would
regularly and smoothly integrate my work, most of it would come right
back to me for fixups.

Don't worry though, if the work is truly variable, someone will pick
up the ball and do the necessary coding style fixups et al. to get it
integrated.
-
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/