All of lore.kernel.org
 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>,
	"Hammer, Gal" <gal.hammer@sap.com>,
	SAP vSMP Linux Maintainer <linux.vsmp@sap.com>
Subject: Re: invalid drv data in show attribute
Date: Mon, 5 Sep 2022 17:12:37 +0200	[thread overview]
Message-ID: <YxYR5SyPB6G5vDXH@kroah.com> (raw)
In-Reply-To: <PAXPR02MB7310E5970299650B7B81B399817F9@PAXPR02MB7310.eurprd02.prod.outlook.com>

On Mon, Sep 05, 2022 at 12:56:29PM +0000, Czerwacki, Eial wrote:
> >And aren't there others at your company that can help you with this?
> afaik, there is not expert on kernel in the company.
> there are some workers that have experience in kernel development but they are from our team

SAP is a big company, I think you should seek them out if you are
wanting to add new subsystems to the kernel to get their help as doing
this is not a trivial task.

> >> I'd prefer not adding complex code to the utils which need to traverse the sysfs tree to collect the right data
> >
> >for device in $(ls /sys/bus/vsmp/device/); do
> now I understand!
> that is what I was missing.
> so inside /sys/bus/vsmp/device/ I can find the following tree?
> 1
> 2
> 3
> ...
> n
> ?

Yes, or how ever you want to name these "boards".

> so I can create entries in /sys/hypervisor/vsmp for the global info

Yes.

> and link /sys/bus/vsmp/device/ to /sys/hypervisor/vsmp/boards?

No symlink needed at all, they are independent things, right?  What
would require such a symlink?

thanks,

greg k-h

  reply	other threads:[~2022-09-05 15:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-04 14:37 invalid drv data in show attribute Czerwacki, Eial
2022-09-05  5:49 ` Greg KH
2022-09-05  6:07   ` Czerwacki, Eial
2022-09-05  7:01     ` Greg KH
2022-09-05  7:28       ` Czerwacki, Eial
2022-09-05 11:41         ` Greg KH
2022-09-05 12:02           ` Czerwacki, Eial
2022-09-05 12:10             ` Greg KH
2022-09-05 12:56               ` Czerwacki, Eial
2022-09-05 15:12                 ` Greg KH [this message]
2022-09-05 15:52                   ` Czerwacki, Eial
2022-09-05 16:02                     ` Greg KH
2022-09-06  7:30                       ` Czerwacki, Eial
2022-09-06 12:09                         ` Greg KH
2022-09-06 12:28                           ` Czerwacki, Eial
2022-09-05  7:07 ` Greg KH
2022-09-05  7:44   ` 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=YxYR5SyPB6G5vDXH@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=eial.czerwacki@sap.com \
    --cc=gal.hammer@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.