mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Eric Farman <farman@linux.ibm.com>, Halil Pasic <pasic@linux.ibm.com>
Cc: Vineeth Vijayan <vneethv@linux.ibm.com>,
	Peter Oberparleiter <oberpar@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>,
	Matthew Rosato <mjrosato@linux.ibm.com>,
	<linux-s390@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<kvm@vger.kernel.org>, <kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] s390/cio: add missing MODULE_DESCRIPTION() macros
Date: Tue, 9 Jul 2024 15:15:45 -0700	[thread overview]
Message-ID: <40298bcf-8c39-4f81-bdb2-afec914fc976@quicinc.com> (raw)
In-Reply-To: <8ae9b1bef0e8ef4689873911c8ae5c9a921401a9.camel@linux.ibm.com>

On 6/19/2024 7:00 AM, Eric Farman wrote:
> On Wed, 2024-06-19 at 12:32 +0200, Halil Pasic wrote:
>> On Tue, 18 Jun 2024 16:11:33 -0400
>> Eric Farman <farman@linux.ibm.com> wrote:
>>
>>>>> +MODULE_DESCRIPTION("VFIO based Physical Subchannel device
>>>>> driver");  
>>>>
>>>> Halil/Mathew/Eric,
>>>> Could you please comment on this ?  
>>>
>>> That's what is in the prologue, and is fine.
>>
>> Eric can you explain it to me why is the attribute "physical"
>> appropriate
>> here? I did a quick grep for "Physical Subchannel" only turned up
>> hits
>> in vfio-ccw.
> 
> One hit, in the prologue comment of this module. "Physical device" adds
> three to the tally, but only one of those is in vfio-ccw so we should
> expand your query regarding "physical" vs "emulated" vs "virtual" in
> the context of, say, tape devices.
> 
>>
>> My best guess is that "physical" was somehow intended to mean the
>> opposite of "virtual". But actually it does not matter if our
>> underlying
>> subchannel is emulated or not, at least AFAIU.
> 
> I also believe this was intended to mean "not virtual," regardless of
> whether there's emulation taking place underneath. That point is moot
> since I don't see that information being surfaced, such that the driver
> can only work with "physical" subchannels.
> 
> I'm fine with removing it if it bothers you, but I don't see it as an
> issue.

Since I'm not the domain expert here I just copied what was in the prologue.
If someone can supply a suitable description, I'll update the patch to use it :)

I'm hoping to have these issued cleaned up tree-wide before the 6.11 merge window.

/jeff


      reply	other threads:[~2024-07-09 22:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-16  3:56 Jeff Johnson
2024-06-18 12:52 ` Vineeth Vijayan
2024-06-18 20:11   ` Eric Farman
2024-06-19 10:32     ` Halil Pasic
2024-06-19 14:00       ` Eric Farman
2024-07-09 22:15         ` Jeff Johnson [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=40298bcf-8c39-4f81-bdb2-afec914fc976@quicinc.com \
    --to=quic_jjohnson@quicinc.com \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=farman@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mjrosato@linux.ibm.com \
    --cc=oberpar@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=svens@linux.ibm.com \
    --cc=vneethv@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

all inboxes | Powered by JetHome®