linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-390@vm.marist.edu,
	linux-s390@vger.kernel.org,
	Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [ANNOUNCE] s390 31 bit kernel support removal
Date: Thu, 13 Feb 2014 14:45:39 +0400	[thread overview]
Message-ID: <52FCA253.3030703@msgid.tls.msk.ru> (raw)
In-Reply-To: <20140212092935.GA14964@osiris>

12.02.2014 13:29, Heiko Carstens wrote:
> We want to remove s390 31 bit kernel support with Linux kernel 3.16.

Maybe you can send a patch for Documentation/feature-removal-schedule.txt
about this now?

Thanks,

/mjt

  reply	other threads:[~2014-02-13 10:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12  9:29 [ANNOUNCE] s390 31 bit kernel support removal Heiko Carstens
2014-02-13 10:45 ` Michael Tokarev [this message]
2014-02-13 10:56   ` Richard Weinberger

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=52FCA253.3030703@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-390@vm.marist.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@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).