From: David Miller <davem@davemloft.net>
To: ursula.braun@de.ibm.com
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com
Subject: Re: [patch 0/9] [RESEND] s390: lcs / ctcm / claw / netiucv patches for 2.6.29
Date: Tue, 24 Mar 2009 15:29:48 -0700 (PDT) [thread overview]
Message-ID: <20090324.152948.107572168.davem@davemloft.net> (raw)
In-Reply-To: <20090324132742.300929000@linux.vnet.ibm.com>
From: Ursula Braun <ursula.braun@de.ibm.com>
Date: Tue, 24 Mar 2009 14:27:42 +0100
> sorry for the resend; I detected compiler and checkpatch warnings in
> patch 8, which are now removed.
>
> Here are a couple of drivers/s390/net-patches for 2.6.29 :
We are past 2.6.29 and are developing 2.6.30
> 1/9: lcs: exploit <linux/kthread.h> - Klaus-Dieter Wacker
> 2/9: lcs: hard_start_xmit return codes - Klaus-Dieter Wacker
> 3/9: netiucv: hard_start_xmit return codes - Ursula Braun
> 4/9: claw: hard_start_xmit return codes - Ursula Braun
> 5/9: ctcm: hard_start_xmit return codes - Ursula Braun
> 6/9: ctcm: avoid wraparound in length of incoming data - Roel Kluin
> 7/9: ctcm: minor findings from code analysis tool - Joel Fowler
> 8/9: claw: convert printk messages to kmsg api - Andy Richter
> 9/9: claw: minor findings from code analysis tool - Andy Richter
As I mentioned net-next-2.6 already has the kmsg patch #8, I
added the rest.
Thanks.
prev parent reply other threads:[~2009-03-24 22:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 13:27 [patch 0/9] [RESEND] s390: lcs / ctcm / claw / netiucv patches for 2.6.29 Ursula Braun
2009-03-24 13:27 ` [patch 1/9] [PATCH] Use kthread instead of kernel_thread Ursula Braun
2009-03-24 13:27 ` [patch 2/9] [PATCH] lcs: invalid return codes from hard_start_xmit Ursula Braun
2009-03-24 13:27 ` [patch 3/9] [PATCH] netiucv: invalid return code " Ursula Braun
2009-03-24 13:27 ` [patch 4/9] [PATCH] claw: invalid return codes " Ursula Braun
2009-03-24 13:27 ` [patch 5/9] [PATCH] ctcm: invalid return code " Ursula Braun
2009-03-24 13:27 ` [patch 6/9] [PATCH] ctcm: avoid wraparound in length of incoming data Ursula Braun
2009-03-24 13:27 ` [patch 7/9] [PATCH] ctcm: fix minor findings from code analysis tool Ursula Braun
2009-03-24 13:27 ` [patch 8/9] [PATCH] kmsg: convert claw printk messages to kmsg api Ursula Braun
2009-03-24 22:28 ` David Miller
2009-03-24 13:27 ` [patch 9/9] [PATCH] claw: fix minor findings from code analysis tool Ursula Braun
2009-03-24 22:29 ` David Miller [this message]
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=20090324.152948.107572168.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=ursula.braun@de.ibm.com \
/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