linux-kernel - Re: [PATCH 0/9] mISDN: fix sparse warnings

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081211210537.GA27010@uranus.ravnborg.org>
Date:	Thu, 11 Dec 2008 22:05:37 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Andrew Morton <akpm@...ux-foundation.org>,
	David Miller <davem@...emloft.net>
Cc:	Karsten Keil <kkeil@...e.de>, hannes@...neseder.net,
	linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH 0/9] mISDN: fix sparse warnings

On Thu, Dec 11, 2008 at 12:22:45PM -0800, Andrew Morton wrote:
> On Wed, 10 Dec 2008 18:30:56 +0100
> Karsten Keil <kkeil@...e.de> wrote:
> 
> > On Tue, Dec 09, 2008 at 08:49:30PM +0100, Hannes Eder wrote:
> > > This series of patches fixes a fair amount of sparse warnings in mISDN.
> > > 
> > 
> > Acked-by: Karsten keil <kkeil@...e.de>
> > 
> > to all.
> > 
> 
> I was going to apply these but
> 
> a) It's nine patches all with the same title and I can't be bothered
>    thinking up useful titles for each one.  See
>    Documentation/SubmittingPatches
> 
> b) I can't find all the patches on lkml.
> 
> c) Why am I applying misdn patches anyway?  If someone else already
>    applied them then they aren't in linux-next.

Lately Davis Miller has included ISDN stuff in net-next.
Try to fix the commented issues, add the acks you got, give patches
proper titles and submit to netdev@...r.kernel.org

	Sam
--
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/