Linux s390 Architecture development
 help / color / mirror / Atom feed
From: Heiko Carstens <hca@linux.ibm.com>
To: Mete Durlu <meted@linux.ibm.com>
Cc: linux-s390@vger.kernel.org
Subject: Re: [PATCH v4] s390/diag204: Introduce diag204 rework
Date: Tue, 27 Oct 2026 15:08:25 +0100	[thread overview]
Message-ID: <20261027140825.11789B74-hca@linux.ibm.com> (raw)
In-Reply-To: <777a0294-2729-4389-a98e-b07fe0f4ae2c@linux.ibm.com>

On Tue, Oct 27, 2026 at 12:53:22PM +0100, Mete Durlu wrote:
> > > + * diag204_init() has to find out, which type of diagnose 204 implementation
> > > + * we have on the machine. Currently there are three possible scanarios:
> > > + *   - subcode 4   + simple data format (only one page)
> > > + *   - subcode 4-6 + extended data format
> > > + *   - subcode 4-7 + extended data format
> > > + *
> > > + * Subcode 5 is used to retrieve the size of the data, provided by subcodes
> > > + * 6 and 7. Subcode 7 basically has the same function as subcode 6. In addition
> > > + * to subcode 6 it provides also information about secondary cpus.
> > > + * In order to get as much information as possible, we first try
> > > + * subcode 7, then 6 and if both fail, we use subcode 4.
> > > + */
> > 
> > This looks like it was copied from the old code: please fix the documentation
> > convert to use imperative mood when you move it.
> 
> Will do! Should it retain the details about which subcodes and
> data formats can exist together?

Sure, I don't see a reason to remove information.

FWIW, it would be helpful if you would reply-to-all, and not only the list :)

      reply	other threads:[~2026-10-27 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 10:40 [PATCH v4] s390/diag204: Introduce diag204 rework Mete Durlu
2026-10-27 10:55 ` sashiko-bot
2026-10-27 11:32 ` Heiko Carstens
2026-10-27 11:53   ` Mete Durlu
2026-10-27 14:08     ` 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=20261027140825.11789B74-hca@linux.ibm.com \
    --to=hca@linux.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=meted@linux.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