public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Czerwacki, Eial" <eial.czerwacki@sap.com>
Cc: "linux-staging@lists.linux.dev" <linux-staging@lists.linux.dev>,
	SAP vSMP Linux Maintainer <linux.vsmp@sap.com>
Subject: Re: [RFC] staging/vSMP: new driver
Date: Thu, 17 Mar 2022 08:23:55 +0100	[thread overview]
Message-ID: <YjLiC82wSBO1oUIq@kroah.com> (raw)
In-Reply-To: <PAXPR02MB73106333FD8FA483FAA0DAC181119@PAXPR02MB7310.eurprd02.prod.outlook.com>

On Wed, Mar 16, 2022 at 06:13:04PM +0000, Czerwacki, Eial wrote:
> Introducing the vSMP guest driver which allows interaction with the vSMP control device when
> running a Linux OS atop of the vSMP hypervisor.
> vSMP is a resource aggregation hypervisor from SAP.
> 
> the driver comprises of 3 modules, vsmp which includes all the api needed to interact with the
> control driver, vsmp_logs which allows reading logs from the hypervisor and vsmp_common_info which
> allows reading generic information the hypervisor exposes, currently only the version is exposed.

Please wrap changelog text at 72 columns, like git asks you to.

Also, why did you not cc: the staging maintainer?  :(

> Signed-off-by: Eial Czerwacki <eial.czerwacki@sap.com>
> ---
>  MAINTAINERS                             |   6 +
>  drivers/staging/Kconfig                 |   2 +
>  drivers/staging/Makefile                |   1 +
>  drivers/staging/vsmp/Kconfig            |  14 +
>  drivers/staging/vsmp/Makefile           |   7 +
>  drivers/staging/vsmp/api.c              | 402 ++++++++++++++++++++++++
>  drivers/staging/vsmp/api.h              |  61 ++++
>  drivers/staging/vsmp/common/Kconfig     |  11 +
>  drivers/staging/vsmp/common/Makefile    |   7 +
>  drivers/staging/vsmp/common/common.c    |  64 ++++
>  drivers/staging/vsmp/common/common.h    |  27 ++
>  drivers/staging/vsmp/common/version.c   |  85 +++++
>  drivers/staging/vsmp/logs/Kconfig       |  10 +
>  drivers/staging/vsmp/logs/Makefile      |   7 +
>  drivers/staging/vsmp/logs/active_logs.c | 112 +++++++
>  drivers/staging/vsmp/registers.h        |  16 +

Without looking at the code, I do not see a TODO file here that lists
the tasks that need to be completed to get this out of the
drivers/staging/ directory.  This is a requirement.

Also, why is this submitted for drivers/staging/ ?  What prevents it
from being merged to the "correct" place in the kernel tree today?

thanks,

greg k-h

  parent reply	other threads:[~2022-03-17  7:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 18:13 [RFC] staging/vSMP: new driver Czerwacki, Eial
2022-03-16 18:31 ` Randy Dunlap
2022-03-16 18:57   ` Czerwacki, Eial
2022-03-17  7:23 ` Greg KH [this message]
2022-03-17  7:34   ` Czerwacki, Eial
2022-03-17  7:51     ` Greg KH
2022-03-17  8:17       ` Czerwacki, Eial
2022-03-17  8:35         ` Greg KH
2022-03-17  8:52           ` Czerwacki, Eial
2022-03-17  8:59             ` Greg KH
2022-03-17  9:04               ` Czerwacki, Eial
2022-04-20 11:18                 ` Czerwacki, Eial
2022-04-20 11:24                   ` Greg KH
2022-04-20 11:38                     ` Czerwacki, Eial
2022-04-20 11:42                       ` Greg KH
2022-04-20 11:57                         ` Czerwacki, Eial
2022-04-20 12:17                           ` Greg KH
2022-04-20 12:36                             ` Czerwacki, Eial
2022-04-20 14:24                               ` Greg KH
2022-03-17  7:24 ` Greg KH
2022-03-17  7:38   ` Czerwacki, Eial
2022-03-17  7:52     ` Greg KH
2022-03-17 10:19 ` Dan Carpenter
2022-03-17 10:27   ` Dan Carpenter
2022-03-17 13:41   ` Czerwacki, Eial
2022-03-17 13:56     ` Dan Carpenter
2022-03-17 14:05       ` Czerwacki, Eial

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=YjLiC82wSBO1oUIq@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=eial.czerwacki@sap.com \
    --cc=linux-staging@lists.linux.dev \
    --cc=linux.vsmp@sap.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