From: Greg KH <greg@kroah.com>
To: Tomek The Messenger <tomekthemessenger@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: the cost of EXPORT_SYMBOL_GPL
Date: Wed, 17 Jun 2020 11:41:19 +0200 [thread overview]
Message-ID: <20200617094119.GA1940079@kroah.com> (raw)
In-Reply-To: <CAA4NGythfRG2eVkwUqq+pUSxT-LC=ESo8=WHzeYsiFp2YuMHNw@mail.gmail.com>
On Wed, Jun 17, 2020 at 11:17:28AM +0200, Tomek The Messenger wrote:
> OK, so I had to wrongly described something because in my company this is
> popular approach to use /sys as some abstract layer to get access to
> registers.
Please do not do that. There are valid kernel apis to grant access to
registers easily, and creating random files and directories in the root
of sysfs is not only the incorrect way of doing it, you are making more
work for yourself to do so, adding more code that is not needed.
Do you have a pointer to the code so that we can provide help with
showing the "correct" way to do all of this?
thanks,
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-06-17 9:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 13:18 the cost of EXPORT_SYMBOL_GPL Tomek The Messenger
2020-06-16 13:27 ` Greg KH
2020-06-17 7:58 ` Tomek The Messenger
2020-06-17 8:55 ` Greg KH
2020-06-17 9:17 ` Tomek The Messenger
2020-06-17 9:28 ` Tomek The Messenger
2020-06-17 9:41 ` Greg KH [this message]
2020-06-17 10:39 ` Tomek The Messenger
2020-06-17 12:24 ` Valdis Klētnieks
2020-06-17 12:31 ` Greg KH
2020-06-17 12:35 ` Martin Kaiser
2020-06-17 12:48 ` Tomek The Messenger
2020-06-17 13:20 ` Valdis Klētnieks
2020-06-17 13:34 ` Ahmad Fatoum
2020-06-17 14:26 ` Tomek The Messenger
2020-06-17 15:08 ` Greg KH
2020-06-17 18:33 ` Valdis Klētnieks
2020-06-17 13:31 ` Greg KH
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=20200617094119.GA1940079@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=tomekthemessenger@gmail.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.