mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Karsten Keil <isdn@linux-pingi.de>,
	David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	i4ldeveloper@listserv.isdn4linux.de,
	Hansjoerg Lipp <hjlipp@web.de>, Karsten Keil <keil@b1-systems.de>,
	stable@kernel.org
Subject: Re: [stable] [PATCH 0/5] late Gigaset fixes for 2.6.35
Date: Mon, 21 Jun 2010 21:02:41 -0700	[thread overview]
Message-ID: <20100622040241.GB4151@kroah.com> (raw)
In-Reply-To: <20100622-patch-gigaset-00.tilman@imap.cc>

On Tue, Jun 22, 2010 at 02:28:41AM +0200, Tilman Schmidt wrote:
> Karsten, David,
> 
> following are five patches to the Gigaset driver fixing reported
> problems with two CAPI applications (Asterisk and capifax). They
> fix serious bugs, though not technically regressions, and I would
> therefore appreciate if they could still make it into release
> 2.6.35. Otherwise please queue them for the first stable cycle.
> 
> These should also go into 2.6.34-stable. They apply cleanly to
> 2.6.34 except for some offsets in file drivers/isdn/gigaset/capi.c.

To get a patch in the -stable tree, please just add a simple:
	Cc: stable <stable@kernel.org>
to the body of the patch in the signed-off-by area.  That way, when the
patches go to Linus, I get automatically notified of them and you don't
have to do anything.  If you don't, then I have to go and dig and watch
the tree to see if they are really applied or not, which, when
confronted with 200+ patches that need to be manually watched for this
way, does not scale...

thanks,

greg k-h

  parent reply	other threads:[~2010-06-22  4:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21 23:54 Tilman Schmidt
2010-06-21 23:54 ` [PATCH 1/5] isdn/gigaset: honor CAPI application's buffer size request Tilman Schmidt
2010-06-21 23:54 ` [PATCH 2/5] isdn/gigaset: correct CAPI voice connection encoding Tilman Schmidt
2010-06-21 23:54 ` [PATCH 3/5] isdn/gigaset: correct CAPI DATA_B3 Delivery Confirmation Tilman Schmidt
2010-06-21 23:55 ` [PATCH 4/5] isdn/gigaset: encode HLC and BC together Tilman Schmidt
2010-06-21 23:55 ` [PATCH 5/5] isdn/gigaset: correct CAPI connection state storage Tilman Schmidt
2010-06-22  4:02 ` Greg KH [this message]
2010-06-26  4:31 ` [PATCH 0/5] late Gigaset fixes for 2.6.35 David Miller

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=20100622040241.GB4151@kroah.com \
    --to=greg@kroah.com \
    --cc=davem@davemloft.net \
    --cc=hjlipp@web.de \
    --cc=i4ldeveloper@listserv.isdn4linux.de \
    --cc=isdn@linux-pingi.de \
    --cc=keil@b1-systems.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stable@kernel.org \
    --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