All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Panin <pazke@donpac.ru>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/13] 2.6.7-rc1-mm1, Simplify DMI matching data
Date: Fri, 28 May 2004 17:46:00 +0400	[thread overview]
Message-ID: <20040528134600.GF7499@pazke> (raw)
In-Reply-To: <20040528132358.GA78847@colin2.muc.de>

[-- Attachment #1: Type: text/plain, Size: 1715 bytes --]

On 149, 05 28, 2004 at 03:23:58PM +0200, Andi Kleen wrote:
> On Fri, May 28, 2004 at 01:54:47PM +0100, Dave Jones wrote:
> > On Fri, May 28, 2004 at 02:18:52PM +0200, Andi Kleen wrote:
> > 
> >  > > simplify DMI blacklist table by removing the need to fill
> >  > > unused slots with NO_MATCH macro.
> >  > 
> >  > Can you please delay that patch for 2.7?
> >  > 2.6 is for bug fixes, not for cleanups.
> >  > 
> >  > There are large third party patchkits for DMI and "cleaning up" 
> >  > the format will just cause lots of rejects and pain. 
> > 
> > Alternatively, those third parties could get their act
> > together and submit those patches back upstream.
> 
> Often this is not the best thing to do - e.g. for upstream it is 
> better to track down the bugs and try to fix them, even if that
> takes a long time or find some other cleaner solution that doesn't
> involve blacklisting. For a third party there are often time constraints 
> (e.g. for a release) where there is no time to track down everything and 
> blacklisting has to be more extensively used.

See the next patch then, it should make life of third party developers
much simpler. Also I can modify the patch to provide NO_MATCH constant,
so there will be no visible differencies.
 
> My point stays that kernel interfaces should stay stable in the stable
> series as far as possible (= unless terminally broken, but that's
> clearly not the case here).  If you feel the need to clean up
> something better wait for the unstable series.

I can't call dmi_scan.c a kernel interface, currently it's a crap.

-- 
Andrey Panin		| Linux and UNIX system administrator
pazke@donpac.ru		| PGP key: wwwkeys.pgp.net

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-05-28 13:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20Oc4-HT-25@gated-at.bofh.it>
2004-05-28 12:18 ` [PATCH 0/13] 2.6.7-rc1-mm1, Simplify DMI matching data Andi Kleen
2004-05-28 12:54   ` Dave Jones
2004-05-28 13:23     ` Andi Kleen
2004-05-28 13:37       ` Christoph Hellwig
2004-05-28 13:46       ` Andrey Panin [this message]
2004-05-28 15:19         ` Andi Kleen
2004-05-28 15:22           ` Dave Jones
2004-05-28 15:42             ` Andi Kleen
2004-05-28 14:39   ` Rik van Riel
2004-06-01 12:46   ` Pavel Machek
2004-05-28 11:55 Andrey Panin

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=20040528134600.GF7499@pazke \
    --to=pazke@donpac.ru \
    --cc=ak@muc.de \
    --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 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.