mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Greg KH <gregkh@suse.de>
Cc: hjlipp@web.de, kkeil@suse.de,
	i4ldeveloper@listserv.isdn4linux.de,
	linux-usb-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, tilman@imap.cc
Subject: Re: [PATCH 0/13] isdn4linux: Siemens Gigaset drivers update
Date: Mon, 3 Apr 2006 20:11:32 -0700	[thread overview]
Message-ID: <20060403201132.3d0f51e7.akpm@osdl.org> (raw)
In-Reply-To: <20060404025818.GA12076@suse.de>

Greg KH <gregkh@suse.de> wrote:
>
> On Tue, Apr 04, 2006 at 02:00:24AM +0200, Hansjoerg Lipp wrote:
> > The following series of patches contains updates to the Siemens Gigaset
> > drivers suggested by various reviewers on lkml. These should go into
> > 2.6.17 if at all possible. Please apply in order.
> 
> Hm, the big merge window for 2.6.17 is past.  If this is a
> single-driver-only update, it might be argued that this should be
> accepted into 2.6.17, but only after it has had a few weeks of testing
> in -mm.  After a few weeks being in -mm however, it will be too late to
> go into 2.6.17.
> 
> So, is 2.6.18 ok?
> 

This driver will be new-in-2.6.17.  Usually after a feature is first merged
in mainline there will be a string of fairly significant updates from the
original development team and from others as things get sorted out.

These patches are almost always good and they're things which we want to
get into the next release, so I tend to ignore the merging rules in this
case, particularly around the -rc1-rc2 timeframe when we have lots of
testing/eyeballing time to go.

Plus these patches provide things which were supposed to be in the initial
merge, only nobody told us..

  reply	other threads:[~2006-04-04  3:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04  0:00 Hansjoerg Lipp
2006-04-04  0:00 ` [PATCH 1/13] isdn4linux: Siemens Gigaset drivers - code cleanup Hansjoerg Lipp
2006-04-04  0:00   ` [PATCH 2/13] isdn4linux: Siemens Gigaset drivers - Kconfig correction Hansjoerg Lipp
2006-04-04  0:00     ` [PATCH 3/13] isdn4linux: Siemens Gigaset drivers - timer usage Hansjoerg Lipp
     [not found]       ` <gigaset307x.2006.04.04.001.4@hjlipp.my-fqdn.de>
2006-04-04  0:00         ` [PATCH 5/13] isdn4linux: Siemens Gigaset drivers - sysfs usage Hansjoerg Lipp
2006-04-04  0:00           ` [PATCH 6/13] isdn4linux: Siemens Gigaset drivers - remove IFNULL macros Hansjoerg Lipp
2006-04-04  0:00             ` [PATCH 7/13] isdn4linux: Siemens Gigaset drivers - uninline Hansjoerg Lipp
2006-04-04  0:00               ` [PATCH 8/13] isdn4linux: Siemens Gigaset drivers - elliminate from_user argument Hansjoerg Lipp
2006-04-04  0:00                 ` [PATCH 9/13] isdn4linux: Siemens Gigaset drivers - mutex conversion Hansjoerg Lipp
2006-04-04  0:00                   ` [PATCH 10/13] isdn4linux: Siemens Gigaset drivers - remove private version of __skb_put() Hansjoerg Lipp
2006-04-04  0:00                     ` [PATCH 11/13] isdn4linux: Siemens Gigaset drivers - remove forward references Hansjoerg Lipp
     [not found]                       ` <gigaset307x.2006.04.04.001.12@hjlipp.my-fqdn.de>
2006-04-04  0:00                         ` [PATCH 13/13] isdn4linux: Siemens Gigaset drivers - make some variables non-atomic Hansjoerg Lipp
2006-04-04  2:58 ` [PATCH 0/13] isdn4linux: Siemens Gigaset drivers update Greg KH
2006-04-04  3:11   ` Andrew Morton [this message]
2006-04-04  3:52     ` 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=20060403201132.3d0f51e7.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=hjlipp@web.de \
    --cc=i4ldeveloper@listserv.isdn4linux.de \
    --cc=kkeil@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=tilman@imap.cc \
    /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

Powered by JetHome