[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100401095900.169b4d00.akpm@linux-foundation.org>
Date: Thu, 1 Apr 2010 09:59:00 -0400
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Miller <davem@...emloft.net>
Cc: herbert@...dor.apana.org.au, henne@...htwindheim.de,
steffen.klassert@...unet.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] padata: section cleanup
On Thu, 01 Apr 2010 00:15:56 -0700 (PDT) David Miller <davem@...emloft.net> wrote:
> From: Andrew Morton <akpm@...ux-foundation.org>
> Date: Wed, 31 Mar 2010 20:29:31 -0400
>
> > Thing is, this isn't net code and it isn't crypto code - it's a
> > kernel-wide utility.
>
> Thanks goodness, because if we had put a private copy in the
> networking or the crypto code someone would have given us a hard time.
>
> Wait a second... we're being given a hard time anyways. :-)
Because the target audience for this work weren't informed about it,
and it would have been better if they had been.
> Kidding aside, why didn't anyone show any interest in the patch when
> it was posted to lkml? You can say it was smoothered together with
> some crypto stuff, but that was absolutely the logical thing to do
> because the follow-on crypto patches showed what the thing was going
> to be used for.
I dunno - these things happen. The padata patch appears to have been
sent once to netdev as an RFC back in 2008 and didn't get any replies
there either. Personally I pay less attention to patches which appear
in the middle of some discussion because I assume they're for
discussion purposes and will come back later.
If I'd known this code was coming I would have reviewed it at an
appropriate time. Probably others are interested also.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists