From: Sam Ravnborg <sam@ravnborg.org>
To: Andrew Morton <akpm@linux-foundation.org>,
David Miller <davem@davemloft.net>
Cc: Karsten Keil <kkeil@suse.de>,
hannes@hanneseder.net, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 0/9] mISDN: fix sparse warnings
Date: Thu, 11 Dec 2008 22:05:37 +0100 [thread overview]
Message-ID: <20081211210537.GA27010@uranus.ravnborg.org> (raw)
In-Reply-To: <20081211122245.754e7829.akpm@linux-foundation.org>
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@suse.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@suse.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@vger.kernel.org
Sam
next prev parent reply other threads:[~2008-12-11 21:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 19:49 [PATCH 0/9] mISDN: fix sparse warnings Hannes Eder
2008-12-10 17:30 ` Karsten Keil
2008-12-11 20:22 ` Andrew Morton
2008-12-11 21:05 ` Sam Ravnborg [this message]
2008-12-13 1:26 ` 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=20081211210537.GA27010@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=hannes@hanneseder.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=kkeil@suse.de \
--cc=linux-kernel@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