linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: s390 patches: descriptions.
Date: Thu, 25 Sep 2003 20:48:16 -0400	[thread overview]
Message-ID: <200309260048.h8Q0mG717733@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1064510341.19756.linux-kernel2news@redhat.com>

> Short descriptions:
>[...]

Are you going to submit zfcp and zcrypt and if yes, when?

-- Pete

       reply	other threads:[~2003-09-26  0:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1064510341.19756.linux-kernel2news@redhat.com>
2003-09-26  0:48 ` Pete Zaitcev [this message]
2003-09-26 14:38 s390 patches: descriptions Martin Schwidefsky
  -- strict thread matches above, loose matches on Subject: below --
2003-09-26 14:16 Martin Schwidefsky
2003-09-26 11:51 Arnd Bergmann
2003-09-26  9:32 Martin Schwidefsky
2003-09-26 13:43 ` Pete Zaitcev
2003-09-25 17:14 Martin Schwidefsky
2003-09-25 17:54 ` Sam Ravnborg
2003-09-11 17:13 s390 patches: Descriptions Martin Schwidefsky

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=200309260048.h8Q0mG717733@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@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).