From: Andrew Morton <akpm@linux-foundation.org>
To: David Miller <davem@davemloft.net>
Cc: herbert@gondor.apana.org.au, henne@nachtwindheim.de,
steffen.klassert@secunet.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] padata: section cleanup
Date: Thu, 1 Apr 2010 09:59:00 -0400 [thread overview]
Message-ID: <20100401095900.169b4d00.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100401.001556.24588152.davem@davemloft.net>
On Thu, 01 Apr 2010 00:15:56 -0700 (PDT) David Miller <davem@davemloft.net> wrote:
> From: Andrew Morton <akpm@linux-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.
next prev parent reply other threads:[~2010-04-01 17:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-27 6:53 [PATCH] padata: section cleanup Henrik Kretzschmar
2010-03-29 7:42 ` Steffen Klassert
2010-03-29 8:15 ` Herbert Xu
2010-03-31 21:58 ` Andrew Morton
2010-04-01 0:24 ` Herbert Xu
2010-03-31 22:04 ` Andrew Morton
2010-04-01 1:38 ` Herbert Xu
2010-04-01 0:29 ` Andrew Morton
2010-04-01 7:15 ` David Miller
2010-04-01 13:59 ` Andrew Morton [this message]
2010-04-01 8:11 ` Steffen Klassert
2010-04-01 21:59 ` Andrew Morton
2010-04-02 1:09 ` Herbert Xu
2010-04-02 11:23 ` Steffen Klassert
2010-04-06 18:00 ` Jonathan Corbet
2010-04-07 13:34 ` Steffen Klassert
2010-04-29 12:14 ` Steffen Klassert
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=20100401095900.169b4d00.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=henne@nachtwindheim.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=steffen.klassert@secunet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.