linux-kernel - Re: [PATCH 0/4] ISDN patches for 2.6.32 (v2)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20090926.202432.51893536.davem@davemloft.net>
Date:	Sat, 26 Sep 2009 20:24:32 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	tilman@...p.cc
Cc:	isdn@...ux-pingi.de, keil@...systems.de,
	i4ldeveloper@...tserv.isdn4linux.de, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] ISDN patches for 2.6.32 (v2)

From: Tilman Schmidt <tilman@...p.cc>
Date: Sat, 26 Sep 2009 13:44:31 +0200

> Hello Karsten,
> 
> is there any chance of getting these and the Gigaset patches forwarded
> for inclusion in 2.6.32 before the merge window closes?
> If not all of them, perhaps at least those which you had already acked
> before David Miller asked that they should formally go through you
> (#2-4 of the ISDN series), and those which are just fixes to the
> existing i4l version of the driver (#1-10 of the Gigaset series)?
> I would really appreciate not having to maintain all of them out of
> tree for another release cycle.

I am extremely disappointed in the lack of respinsiveness of Karsten
to ISDN patches.  He wants to handle them, but he has effectively
disappeared during the most critical time for patch integration, which
is during the merge window.

If he's busy in life or whatever, that's fine, but in such a case he
should appoint someone to handle ISDN patches until he does have time.

And if no ISDN expert is available, Tilman's suggestion of letting
me integrate the patches should be taken.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/