From: David Miller <davem@davemloft.net>
To: tilman@imap.cc
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
i4ldeveloper@listserv.isdn4linux.de, hjlipp@web.de,
isdn@linux-pingi.de
Subject: Re: [PATCH 00/12] Gigaset driver patches for 2.6.32
Date: Mon, 07 Sep 2009 02:18:08 -0700 (PDT) [thread overview]
Message-ID: <20090907.021808.57016299.davem@davemloft.net> (raw)
In-Reply-To: <4AA4CE49.7040501@imap.cc>
From: Tilman Schmidt <tilman@imap.cc>
Date: Mon, 07 Sep 2009 11:11:37 +0200
> David Miller schrieb:
>> From: Tilman Schmidt <tilman@imap.cc>
>> Date: Sun, 6 Sep 2009 20:58:52 +0200 (CEST)
>>
>>> Would you please take these into your net tree for 2.6.32.
>>
>> So do we have an ISDN maintainer or not?
>>
>> If Karsten is still maintaining things, your work should
>> go through him not me.
>
> Last atime I asked, you said me you would take ISDN patches.
> Could you two please sort this out?
Sure.
Karsten, are you going to handle ISDN and ISDN driver patches
and queue them up to me?
> I am just a humble driver maintainer knowing nothing about
> maintainer politics.
Understood.
next prev parent reply other threads:[~2009-09-07 9:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 18:58 [PATCH 00/12] Gigaset driver patches for 2.6.32 Tilman Schmidt
2009-09-06 18:58 ` [PATCH 05/12] gigaset: announce if built with debugging Tilman Schmidt
2009-09-06 18:58 ` [PATCH 11/12] gigaset: allow building without I4L Tilman Schmidt
2009-09-06 18:58 ` [PATCH 01/12] gigaset: really fix chars_in_buffer Tilman Schmidt
2009-09-06 18:58 ` [PATCH 09/12] gigaset: add kerneldoc comments Tilman Schmidt
2009-09-06 18:58 ` [PATCH 02/12] gigaset: fix reject/hangup handling Tilman Schmidt
2009-09-06 18:58 ` [PATCH 06/12] gigaset: fix device ERROR response handling Tilman Schmidt
[not found] ` <20090906-patch-gigaset-00.tilman-ZTO5kqT2PaM@public.gmane.org>
2009-09-06 18:58 ` [PATCH 12/12] gigaset: add Kernel CAPI interface Tilman Schmidt
2009-09-06 18:58 ` [PATCH 03/12] gigaset: linearize skb Tilman Schmidt
2009-09-06 18:58 ` [PATCH 04/12] gigaset: handle isoc frame errors more gracefully Tilman Schmidt
2009-09-06 18:58 ` [PATCH 08/12] gigaset: correct debugging output selection Tilman Schmidt
2009-09-06 18:58 ` [PATCH 07/12] gigaset: improve error recovery Tilman Schmidt
[not found] ` <20090906-patch-gigaset-07.tilman-ZTO5kqT2PaM@public.gmane.org>
2009-09-07 8:59 ` [PATCH 07/12 v2] " Tilman Schmidt
2009-09-06 18:58 ` [PATCH 10/12] gigaset: prepare for CAPI implementation Tilman Schmidt
2009-09-07 1:26 ` [PATCH 00/12] Gigaset driver patches for 2.6.32 Daniel Walker
2009-09-07 9:07 ` Tilman Schmidt
2009-09-07 14:30 ` Daniel Walker
2009-09-07 9:00 ` David Miller
2009-09-07 9:11 ` Tilman Schmidt
2009-09-07 9:18 ` David Miller [this message]
2009-09-07 18:56 ` Karsten Keil
-- strict thread matches above, loose matches on Subject: below --
2009-09-09 22:32 Tilman Schmidt
[not found] <20090909223205.E9D632269516@fifo99.com>
2009-09-10 3:47 ` Daniel Walker
2009-09-10 3:51 ` David Miller
2009-09-10 14:05 Tilman Schmidt
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=20090907.021808.57016299.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hjlipp@web.de \
--cc=i4ldeveloper@listserv.isdn4linux.de \
--cc=isdn@linux-pingi.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).