From: Ingo Molnar <mingo@elte.hu>
To: Guillaume Chazarain <guichaz@yahoo.fr>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Dropping some patches from sched-devel
Date: Fri, 25 Jan 2008 17:58:37 +0100 [thread overview]
Message-ID: <20080125165837.GA19377@elte.hu> (raw)
In-Reply-To: <3d8471ca0801250838h2d1f21f2n95c70bc26e28d310@mail.gmail.com>
* Guillaume Chazarain <guichaz@yahoo.fr> wrote:
> Hi Ingo,
>
> Can I talk you into dropping these patches of mine from sched-devel
> (or not send them to Linus):
>
> da0f9440cdcb1edd5424de91f326de83de3fe5f9 sched: make sure jiffies is
> up to date before calling __update_rq_clock()
> 6eb300ad38fef6db4efe177067a65aaa771596da sched: fix rq->clock
> overflows detection with CONFIG_NO_HZ
>
> They are not of good enough quality, and I'm working on a better
> approach.
sure, done.
what method are you using of determining quality? Could you perhaps try
to automate it? (even better would be some self-test within the kernel
that detects badness)
Ingo
next prev parent reply other threads:[~2008-01-25 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 16:38 Dropping some patches from sched-devel Guillaume Chazarain
2008-01-25 16:58 ` Ingo Molnar [this message]
2008-01-25 17:27 ` Guillaume Chazarain
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=20080125165837.GA19377@elte.hu \
--to=mingo@elte.hu \
--cc=guichaz@yahoo.fr \
--cc=linux-kernel@vger.kernel.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