public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mingo@elte.hu
Cc: stefanr@s5r6.in-berlin.de, cate@cateee.net, rjw@sisk.pl,
	Valdis.Kletnieks@vt.edu, torvalds@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: using LKML for subsystem development
Date: Sat, 26 Jan 2008 06:07:05 -0800 (PST)	[thread overview]
Message-ID: <20080126.060705.53192768.davem@davemloft.net> (raw)
In-Reply-To: <20080126112820.GA10563@elte.hu>

From: Ingo Molnar <mingo@elte.hu>
Date: Sat, 26 Jan 2008 12:28:20 +0100

> Filter on all mails from David S. Miller if you are interested in 
> networking topics. You'll have a really good grasp of what's going on in 
> that area, without having to invest too much time.

That's a very poor filter, I don't write much code lately in the
networking.

I only provide theoretical direction in a few specific areas I care
about.

As Ingo already knows, I think this "put everything on lkml" argument
is bogus.

And about bisectability, every time I apply a networking patch I do at
the very least a "allmodconfig" build with just that new patch added,
for every patch.  Often I do more extensive build testing.

And when I rebase the tree, I rerun this check after each
patch gets re-applied to a new base tree.

In fact I'm working on such issues as I fly over the Australia
for LCA08 :-)

So this isn't an issue that posting to lkml is going to help.

  reply	other threads:[~2008-01-26 14:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24 23:17 Linux 2.6.24 Linus Torvalds
2008-01-24 23:41 ` Linus Torvalds
2008-01-25  9:10   ` Giacomo A. Catenazzi
2008-01-25  9:58     ` Valdis.Kletnieks
2008-01-25 11:58       ` Rafael J. Wysocki
2008-01-25 12:34         ` Giacomo A. Catenazzi
2008-01-25 23:50           ` Stefan Richter
2008-01-26  0:42             ` using LKML for subsystem development (was Re: Linux 2.6.24) Stefan Richter
2008-01-26  3:28               ` Valdis.Kletnieks
2008-01-26 13:31                 ` using LKML for subsystem development Stefan Richter
2008-01-27  7:37                   ` Valdis.Kletnieks
2008-01-26 11:28               ` using LKML for subsystem development (was Re: Linux 2.6.24) Ingo Molnar
2008-01-26 14:07                 ` David Miller [this message]
2008-01-26 14:45                   ` using LKML for subsystem development Stefan Richter
2008-01-26 14:25                 ` Stefan Richter
2008-02-01  9:40                   ` Ingo Molnar
2008-02-01 19:53                     ` Stefan Richter
2008-01-26  3:19             ` Linux 2.6.24 Valdis.Kletnieks
2008-01-25 11:35     ` Ingo Molnar
2008-01-25 10:11 ` [PATCH] linux-2.6.24/drivers/hid/hid-input.c Philipp Matthias Hahn
2008-01-25 10:30   ` Jiri Kosina
2008-02-03 12:35 ` Linux 2.6.24 Jan Engelhardt

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=20080126.060705.53192768.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=cate@cateee.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=torvalds@linux-foundation.org \
    /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