From: Chris Friesen <chris.friesen@genband•com>
To: Tom St Denis <tstdenis@elliptictech•com>
Cc: Steven Rostedt <rostedt@goodmis•org>,
David Dillow <dave@thedillows•org>,
Borislav Petkov <bp@alien8•de>,
linux-kernel@vger•kernel.org, netdev@vger•kernel.org
Subject: Re: IPsec AH use of ahash
Date: Mon, 21 Jan 2013 09:49:19 -0600 [thread overview]
Message-ID: <50FD637F.2080604@genband.com> (raw)
In-Reply-To: <1161725580.95543.1358782288077.JavaMail.root@elliptictech.com>
On 01/21/2013 09:31 AM, Tom St Denis wrote:
> ----- Original Message -----
>> From: "Steven Rostedt"<rostedt@goodmis•org> To: "Tom St
>> Denis"<tstdenis@elliptictech•com> Cc: "David
>> Dillow"<dave@thedillows•org>, "Borislav Petkov"<bp@alien8•de>,
>> linux-kernel@vger•kernel.org, netdev@vger•kernel.org Sent: Monday,
>> 21 January, 2013 10:28:33 AM Subject: Re: IPsec AH use of ahash
>>
>> When I send a patch to another maintainer, and they tell me to fix
>> the way I did the comments, I don't complain. I fix the comments
>> and resend.
>
> Which is less of a problem when there is a timeliness factor. In the
> business world people move on and don't work at that pace.
There can be an impedance mismatch between the "get it done to hit a
deadline" business world and the "get it right no matter how long it
takes" world of some open-source projects.
However, many businesses have recognized that they get far more benefit
from dealing with open-source than it costs them in designer time.
From the point of view of my employer (I work in telecom) the choices
are either:
a) work with the kernel to get the code submitted into mainline
b) keep the changes private and port them every time we upgrade
Over a decade or more my management has come to realize that option "a"
is generally better in the long term, even if it's a bit more effort in
the short term.
There are exceptions of course, and sometimes we just need to do a
quick-and-dirty solution to get something out the door.
Chris
next prev parent reply other threads:[~2013-01-21 15:50 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <528051367.70594.1358268708738.JavaMail.root@elliptictech.com>
2013-01-16 6:21 ` IPsec AH use of ahash Steffen Klassert
2013-01-18 19:35 ` Tom St Denis
2013-01-18 19:50 ` David Miller
2013-01-18 20:53 ` Tom St Denis
2013-01-18 22:16 ` Waskiewicz Jr, Peter P
2013-01-18 22:31 ` Tom St Denis
2013-01-19 2:33 ` Michal Kubecek
2013-01-19 2:59 ` Tom St Denis
2013-01-19 3:59 ` Eric Dumazet
2013-01-19 10:30 ` Tom St Denis
2013-01-19 15:46 ` Eric Dumazet
2013-01-20 5:06 ` Mike Galbraith
2013-01-20 10:31 ` Borislav Petkov
2013-01-20 12:56 ` Tom St Denis
2013-01-20 13:34 ` Alexander Holler
2013-01-20 13:54 ` Tom St Denis
2013-01-30 22:16 ` Jan Engelhardt
2013-01-20 22:07 ` Steven Rostedt
2013-01-21 0:47 ` Tom St Denis
2013-01-20 12:55 ` Tom St Denis
2013-01-20 14:11 ` Mike Galbraith
2013-01-20 15:07 ` Tom St Denis
2013-01-20 16:34 ` David Dillow
2013-01-20 17:40 ` Tom St Denis
2013-01-20 18:11 ` David Dillow
2013-01-20 18:47 ` Tom St Denis
2013-01-20 22:54 ` Steven Rostedt
2013-01-21 0:34 ` Borislav Petkov
2013-01-21 0:40 ` Tom St Denis
2013-01-21 1:08 ` Borislav Petkov
2013-01-21 9:18 ` David Dillow
2013-01-21 10:20 ` Tom St Denis
2013-01-21 13:38 ` Steven Rostedt
2013-01-21 13:45 ` Tom St Denis
2013-01-21 14:37 ` Steven Rostedt
2013-01-21 14:51 ` Tom St Denis
2013-01-21 15:28 ` Steven Rostedt
2013-01-21 15:31 ` Tom St Denis
2013-01-21 15:49 ` Chris Friesen [this message]
2013-01-21 16:05 ` Tom St Denis
2013-01-20 20:30 ` Alan Cox
2013-01-21 0:46 ` Tom St Denis
2013-01-20 17:03 ` H. Peter Anvin
2013-01-20 17:33 ` Tom St Denis
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=50FD637F.2080604@genband.com \
--to=chris.friesen@genband$(echo .)com \
--cc=bp@alien8$(echo .)de \
--cc=dave@thedillows$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=rostedt@goodmis$(echo .)org \
--cc=tstdenis@elliptictech$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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