From: Pete Zaitcev <zaitcev@redhat.com>
To: schwidefsky@de.ibm.com
Cc: linux-kernel@vger.kernel.org, Pete Zaitcev <zaitcev@redhat.com>
Subject: 2.4.19-pre3 s390 memorandum
Date: Fri, 15 Mar 2002 13:15:23 -0500 [thread overview]
Message-ID: <20020315131523.A24597@devserv.devel.redhat.com> (raw)
Martin,
thanks for taking action and sending updates for 2.4.19-pre3.
I am happy to report that it generally works, and with the
partition code it recognises ECKD volumes.
I would very much prefer if you sent future updates in plain
diff -u to linux-kernel too. I appreciate tarballs that you
sent to me, but this is not quite what would prevent broken
kernels in the future [it helps Red Hat to ship working kernels,
but it does not help Marcelo]. As it was with 2.4.18, Marcelo
has no choice but to accept all code that belongs to your
authority and to fail every else, producing inconsistency.
Posting to linux-kernel beforehand is supposed to start a
discussion that may guide Marcelo to accept changes to generic code.
I will send the example with the partition code immediately.
Greetings,
-- Pete
next reply other threads:[~2002-03-15 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 18:15 Pete Zaitcev [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-18 14:03 2.4.19-pre3 s390 memorandum 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=20020315131523.A24597@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