linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Adrian Bunk <bunk@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Dan Williams <dan.j.williams@intel.com>,
	linux-ext4@vger.kernel.org, netdev@vger.kernel.org,
	linux-ide@vger.kernel.org,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	marek.vasut@gmail.com, David Woodhouse <dwmw2@infradead.org>,
	Mark Fasheh <mark.fasheh@oracle.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	linuxppc-dev@ozlabs.org
Subject: Re: powerpc allmodconfig
Date: Thu, 16 Oct 2008 10:43:33 +0200	[thread overview]
Message-ID: <s5hod1lorpm.wl%tiwai@suse.de> (raw)
In-Reply-To: <20081016082157.GC23630@cs181140183.pp.htv.fi>

At Thu, 16 Oct 2008 11:21:57 +0300,
Adrian Bunk wrote:
> 
> On Thu, Oct 16, 2008 at 09:57:11AM +0200, Takashi Iwai wrote:
> > At Thu, 16 Oct 2008 10:38:36 +0300,
> > Adrian Bunk wrote:
> > > 
> > > On Thu, Oct 16, 2008 at 07:57:29AM +0200, Takashi Iwai wrote:
> > > > At Wed, 15 Oct 2008 21:33:37 -0700,
> > > > Andrew Morton wrote:
> > > > > 
> > > > > sound/soc/soc-dapm.c:1029: warning: 'snd_soc_dapm_connect_input' is deprecated (declared at sound/soc/soc-dapm.c:1026)
> > > > > sound/soc/soc-dapm.c:1029: warning: 'snd_soc_dapm_connect_input' is deprecated (declared at sound/soc/soc-dapm.c:1026)
> > > > 
> > > > These are definitions of deprecated interfaces.
> > > > We can remove it in 2.6.29.  If we don't want to be conservative, it
> > > > can be removed in 2.6.28, too.
> > > >...
> > > 
> > > Since it's an in-kernel API there's no reason to keep it once there are 
> > > no users left.
> > 
> > Right.  But, IMO, now is no suitable time.
> > A thing like API removal should have been tested in linux-next, and we
> > had plenty of time indeed for 2.6.28.
> >...
> 
> A grep through the tree and one test compile that covers 
> sound/soc/soc-dapm.c should be enough testing.
> 
> And having it then in -next once should be enough to discover if someone 
> wrongly added a new user.

My point is the time for removal.  The API changes should have been
done in the merge window, and it should have been tested *before* the
merge window.

> I have removed many functions in the kernel, and there isn't much that 
> can go wrong - even adding a PCI ID to a driver has a bigger risk of 
> introducing a regression.

Yeah, IMHO, adding PCI IDs blindly at the late stage should be
avoided, too, although many people love that.


thanks,

Takashi

  reply	other threads:[~2008-10-16  8:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16  4:33 powerpc allmodconfig Andrew Morton
2008-10-16  4:56 ` Benjamin Herrenschmidt
2008-10-16  5:02 ` David Miller
2008-10-16  5:21   ` Benjamin Herrenschmidt
2008-10-16  6:08   ` Dan Williams
2008-10-16  6:55     ` Brice Goglin
2008-10-16  6:58       ` David Miller
2008-10-16 16:22         ` Jesse Brandeburg
2008-10-16  7:31   ` Geert Uytterhoeven
2008-10-16  7:36     ` David Miller
2008-10-16  7:58       ` Geert Uytterhoeven
2008-10-16 14:57   ` Johannes Berg
2008-10-16 19:49     ` David Miller
2008-10-16 20:02       ` Arjan van de Ven
2008-10-18 12:20         ` Johannes Berg
2008-10-17 11:09   ` Ingo Molnar
2008-10-16  5:57 ` Takashi Iwai
2008-10-16  7:38   ` Adrian Bunk
2008-10-16  7:57     ` Takashi Iwai
2008-10-16  8:21       ` Adrian Bunk
2008-10-16  8:43         ` Takashi Iwai [this message]
2008-10-16 10:03           ` Adrian Bunk
2008-10-16  9:34 ` Mark Brown

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=s5hod1lorpm.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=bzolnier@gmail.com \
    --cc=dan.j.williams@intel.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=marek.vasut@gmail.com \
    --cc=mark.fasheh@oracle.com \
    --cc=mchehab@infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=ralf@linux-mips.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;
as well as URLs for NNTP newsgroup(s).