netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: davem@davemloft.net, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Cc: Hansjoerg Lipp <hjlipp@web.de>
Subject: [PATCH 0/3] gigaset: late patches for 2.6.30
Date: Sun,  5 Apr 2009 18:39:32 +0200 (CEST)	[thread overview]
Message-ID: <20090404-patch-00.tilman@imap.cc> (raw)

Dave,

following are three last-minute patches to the Gigaset driver
for kernel release 2.6.30. As they are rather low-impact bug and
documentation fixes I hope they can still be included.

Thanks,
Tilman

             reply	other threads:[~2009-04-05 16:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-05 16:39 Tilman Schmidt [this message]
2009-04-05 16:39 ` [PATCH 1/3] bas_gigaset: use tasklet_hi_schedule for timing critical tasklets Tilman Schmidt
2009-04-07  0:43   ` David Miller
2009-04-05 16:39 ` [PATCH 3/3] gigaset: documentation update Tilman Schmidt
2009-04-07  0:43   ` David Miller
2009-04-05 16:39 ` [PATCH 2/3] gigaset: in file ops, check for device disconnect before anything else Tilman Schmidt
2009-04-07  0:43   ` 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=20090404-patch-00.tilman@imap.cc \
    --to=tilman@imap.cc \
    --cc=davem@davemloft.net \
    --cc=hjlipp@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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).