public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bryan O'Sullivan" <bos@serpentine.com>
To: William D Waddington <william.waddington@beezmo.com>
Cc: Arjan van de Ven <arjan@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [RFCLUE3] flagging kernel interface changes
Date: Wed, 15 Nov 2006 17:05:34 -0800	[thread overview]
Message-ID: <455BB95E.8090600@serpentine.com> (raw)
In-Reply-To: <455B96C7.8010202@beezmo.com>

William D Waddington wrote:

> The other part of the question is why this irq_handler prototype change
> in 2.6.19 isn't flagged to make things a little easier.

For in-tree drivers, it broke the compilation of any drivers that relied 
upon it, and they were then fixed, and most of the fixing occurred 
before the changes made it into any widely used tree.  That 
break-it-and-fix-it approach is typically seen as flagging enough.  If 
your driver isn't in-tree, it's invisible to kernel maintainers.

For out-of-tree drivers, your best bet is to follow Jonathan Corbet's 
notes on LWN.  He's pretty good about describing impending widespread 
breakage before it hits the main tree.

	<b

  reply	other threads:[~2006-11-16  1:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15 22:14 [RFCLUE3] flagging kernel interface changes William D Waddington
2006-11-15 22:25 ` Arjan van de Ven
2006-11-15 22:37   ` William D Waddington
2006-11-16  1:05     ` Bryan O'Sullivan [this message]
2006-11-15 23:17 ` Jesper Juhl
2007-01-21 19:15   ` William D Waddington

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=455BB95E.8090600@serpentine.com \
    --to=bos@serpentine.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=william.waddington@beezmo.com \
    /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