From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Frank Pavlic <fpavlic@de.ibm.com>
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [RESEND PATCH 0/7] [S390]: Introduction of AF_IUCV sockets support
Date: Tue, 6 Feb 2007 09:30:02 +0100 [thread overview]
Message-ID: <20070206083002.GA9946@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20070205140050.GA19137@de.ibm.com>
On Mon, Feb 05, 2007 at 03:00:50PM +0100, Frank Pavlic wrote:
> Hello,
> seems that Patch 1/7 is lost and did not make its way to the mailing list :-(
> That's the reason why I resend the whole patch set again.
> Here we go ...
> [...]
> [1/7] [S390]: Rewrite of the IUCV base code, part 1
Patch 1 has more than 100.000 characters. That's why it didn't reach any
list.
prev parent reply other threads:[~2007-02-06 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 14:00 [RESEND PATCH 0/7] [S390]: Introduction of AF_IUCV sockets support Frank Pavlic
2007-02-06 8:30 ` Heiko Carstens [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=20070206083002.GA9946@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=fpavlic@de.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).