public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Thomas Huth <thuth@redhat.com>,
	linux-doc@vger.kernel.org,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Janosch Frank <frankja@linux.ibm.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	linux-s390@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [PATCH] Documentation: Add "S390" to the swiotlb kernel parameter
Date: Mon, 17 Jun 2024 16:14:44 -0600	[thread overview]
Message-ID: <87bk3zi5d7.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20240614081438.553160-1-thuth@redhat.com>

Thomas Huth <thuth@redhat.com> writes:

> The "swiotlb" kernel parameter is used on s390 for protected virt since
> commit 64e1f0c531d1 ("s390/mm: force swiotlb for protected virtualization")
> and thus should be marked in kernel-parameters.txt accordingly.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---

Applied, thanks.

For the record, this is a great set of cleanups, thanks for doing this.

>  PS: I wonder whether we could remove IA-64 nowadays...?

Yes, references to IA-64 should come out at this point.  If you want to
do that, I'd suggest doing it as one big patch...  in theory, that
architecture could come back if enough maintenance initiative is shown.
I don't think it will happen but, if it does, it would be nice to be
able to undo the docs change with a single revert.

Thanks,

jon

      parent reply	other threads:[~2024-06-17 22:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14  8:14 [PATCH] Documentation: Add "S390" to the swiotlb kernel parameter Thomas Huth
2024-06-14 11:34 ` Christian Borntraeger
2024-06-14 12:39 ` Claudio Imbrenda
2024-06-17 22:14 ` Jonathan Corbet [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=87bk3zi5d7.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=svens@linux.ibm.com \
    --cc=thuth@redhat.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