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/2] s390: claw and ctcm patches
Date: Thu, 12 Aug 2010 16:04:49 -0700 (PDT) [thread overview]
Message-ID: <20100812.160449.260100327.davem@davemloft.net> (raw)
In-Reply-To: <20100812115826.983015000@linux.vnet.ibm.com>
From: Ursula Braun <ursula.braun@de.ibm.com>
Date: Thu, 12 Aug 2010 13:58:26 +0200
> these patches repair warnings seen with the linux-2.6.git 2.6.35
> caused by the used constants READ / WRITE.
>
> The patches apply on linux-2.6.git and net-next-2.6.git.
Both applied, thanks.
prev parent reply other threads:[~2010-08-12 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 11:58 [patch 0/2] s390: claw and ctcm patches Ursula Braun
2010-08-12 11:58 ` [patch 1/2] [PATCH] claw: rename READ/WRITE defines to avoid redefinitions Ursula Braun
2010-08-12 11:58 ` [patch 2/2] [PATCH] ctcm: " Ursula Braun
2010-08-12 23:04 ` 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=20100812.160449.260100327.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;
as well as URLs for NNTP newsgroup(s).