public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andre Tomt <andre@tomt.net>
To: Greg KH <greg@kroah.com>
Cc: Adrian Bunk <bunk@stusta.de>, Chris Wright <chrisw@osdl.org>,
	torvalds@osdl.org, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFQ] Rules for accepting patches into the linux-releases tree
Date: Sat, 05 Mar 2005 19:31:04 +0100	[thread overview]
Message-ID: <4229FAE8.6050107@tomt.net> (raw)
In-Reply-To: <20050305174055.GB13104@kroah.com>

Greg KH wrote:
> On Sat, Mar 05, 2005 at 02:59:17PM +0100, Adrian Bunk wrote:
>>An example that doesn't fit:
>>
>>A patch of me to remove an unused function was accepted into 2.6.11 .
>>Today, someone mailed that there's an external GPL'ed module that uses 
>>this function.
>>
>>A patch to re-add this function as it was in 2.6.10 does not fulfill 
>>your criteria, but it is a low-risk way to fix a regression compared to 
>>2.6.10 .
> 
> 
> Yes, I wouldn't have a problem with adding this kind of fix.  Do others
> disagree?

Depends. Is Linus going to push it back into his tree? If it's just 
something like the remap_page_range going away, fix the the module 
instead, I'd say.

  reply	other threads:[~2005-03-05 18:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 22:21 [RFQ] Rules for accepting patches into the linux-releases tree Greg KH
2005-03-05  5:08 ` Ian Pilcher
2005-03-05  5:52   ` Dave Kleikamp
2005-03-05  8:19   ` Valdis.Kletnieks
2005-03-05 12:39   ` Ed Tomlinson
2005-03-05  9:58 ` Adam Sampson
2005-03-05 17:42   ` Greg KH
2005-03-05 18:26   ` Randy.Dunlap
2005-03-05 10:43 ` Andries Brouwer
2005-03-05 17:42   ` Greg KH
2005-03-06 17:10   ` Andres Salomon
2005-03-06 20:10     ` Adam Kropelin
2005-03-07  8:32       ` Andres Salomon
2005-03-07  7:50     ` Paul Jackson
2005-03-07  8:14       ` Andres Salomon
2005-03-05 13:59 ` Adrian Bunk
2005-03-05 17:40   ` Greg KH
2005-03-05 18:31     ` Andre Tomt [this message]
2005-03-05 20:01     ` Ian Pilcher
2005-03-06  9:44 ` Marcelo Tosatti
2005-03-07 17:35   ` John W. Linville
2005-03-06 11:20 ` Joel Becker
2005-03-06 11:23 ` Jesper Juhl
  -- strict thread matches above, loose matches on Subject: below --
2005-03-04 20:36 [PATCH] I2C: lm80 driver improvement Greg KH
2005-03-05  5:57 ` [RFQ] Rules for accepting patches into the linux-releases tree Shawn Starr
2005-03-05  6:11   ` Randy.Dunlap
2005-03-05 16:33   ` Greg KH

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=4229FAE8.6050107@tomt.net \
    --to=andre@tomt.net \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=chrisw@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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