mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "SL Baur" <steve@xemacs.org>
To: "David Miller" <davem@davemloft.net>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org, akpm@linux-foundation.org,
	viro@zeniv.linux.org.uk
Subject: Re: CONFIG_OPTIMIZE_INLINING
Date: Sun, 27 Apr 2008 02:10:06 -0700	[thread overview]
Message-ID: <ed10ee420804270210y219ac4dbne858906233ab9691@mail.gmail.com> (raw)
In-Reply-To: <20080426.230807.144232984.davem@davemloft.net>

On 4/26/08, David Miller <davem@davemloft.net> wrote:

>  Because anyone who is paying attention can see clearly that you're
>  trying to push as much stuff as quickly as possible into Linus's tree

I'm giving up for the moment trying to review anything.  I can't contribute
by compile testing a lot of stuff - I don't have a farm of computers that can
build and boot thousands of kernels overnight, nor a machine that can build
a kernel in 2 minutes, nor a suite of cross-compilers that can test
build patches
across all the architectures we support.  I'm not paid to follow any of this, my
only paid concern is Linux userland and so following Linux Kernel is a hobby.

If you, Ingo, are going to push patches in before they can be reviewed, what
reason is there for anyone to bother trying?  (The patch I was trying to review
that you merged before review was complete was different than this one).

Oh and Thank You! David for starting to post your git pull messages.  Idiots
like me read those sorts of things and appreciate it *very* much.

-sb  (I *like* reading patches and I want to contribute any way I can)

  parent reply	other threads:[~2008-04-27  9:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27  4:55 CONFIG_OPTIMIZE_INLINING David Miller
2008-04-27  5:59 ` CONFIG_OPTIMIZE_INLINING Ingo Molnar
2008-04-27  6:08   ` CONFIG_OPTIMIZE_INLINING David Miller
2008-04-27  8:20     ` CONFIG_OPTIMIZE_INLINING Ingo Molnar
2008-04-27  9:10     ` SL Baur [this message]
2008-04-27  9:16       ` CONFIG_OPTIMIZE_INLINING Dave Airlie
2008-04-27  9:21         ` CONFIG_OPTIMIZE_INLINING David Miller
2008-04-27 12:13           ` CONFIG_OPTIMIZE_INLINING Ingo Molnar
2008-04-27 11:22     ` CONFIG_OPTIMIZE_INLINING Ingo Molnar
2008-04-27 17:25     ` CONFIG_OPTIMIZE_INLINING Pavel Machek
2008-04-28 10:42       ` CONFIG_OPTIMIZE_INLINING Adrian Bunk
2008-04-27  6:26   ` CONFIG_OPTIMIZE_INLINING Christoph Hellwig
2008-04-27 10:56     ` CONFIG_OPTIMIZE_INLINING Sam Ravnborg
2008-04-27  6:02 ` CONFIG_OPTIMIZE_INLINING Sam Ravnborg

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=ed10ee420804270210y219ac4dbne858906233ab9691@mail.gmail.com \
    --to=steve@xemacs.org \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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

all inboxes | Powered by JetHome®