From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Yu, Lang" <Lang.Yu@amd.com>
Cc: Joe Perches <joe@perches.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sysfs: Remove page boundary align limitation on sysfs_emit and sysfs_emit_at
Date: Wed, 8 Sep 2021 15:04:06 +0200 [thread overview]
Message-ID: <YTi0xkTVYqUpKXSt@kroah.com> (raw)
In-Reply-To: <DM6PR12MB4250302F4EB80233D5807CB6FBD49@DM6PR12MB4250.namprd12.prod.outlook.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Wed, Sep 08, 2021 at 12:52:43PM +0000, Yu, Lang wrote:
> [AMD Official Use Only]
>
> Thanks for your reply.
> Just curious if we don't put such a limitation, what are the consequences?
> If we remove the limitation, sys_emit/sys_emit_at api will be more flexible.
> Since the comments of sysfs_emit/ sys_emit_at api are
> " sysfs_emit - scnprintf equivalent, aware of PAGE_SIZE buffer. ",
> Why not make them more equivalent with scnprintf?
Because this is not a general replacement for scnprintf(), it is only to
be used with sysfs files.
Where else are you wanting to use these functions that this patch woulud
be required that does not haver to deal with sysfs?
thanks,
greg k-h
next prev parent reply other threads:[~2021-09-08 13:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 12:07 [PATCH] sysfs: Remove page boundary align limitation on sysfs_emit and sysfs_emit_at Lang Yu
2021-09-08 12:32 ` Greg Kroah-Hartman
2021-09-08 12:52 ` Yu, Lang
2021-09-08 13:04 ` Greg Kroah-Hartman [this message]
2021-09-08 13:21 ` Yu, Lang
2021-09-08 13:49 ` Greg Kroah-Hartman
2021-09-08 15:33 ` Yu, Lang
2021-09-09 5:19 ` Greg Kroah-Hartman
2021-09-09 5:31 ` Yu, Lang
2021-09-09 6:05 ` Greg Kroah-Hartman
2021-09-09 5:05 ` Joe Perches
2021-09-09 5:27 ` Yu, Lang
2021-09-09 5:34 ` Greg Kroah-Hartman
2021-09-09 5:59 ` Yu, Lang
2021-09-09 6:07 ` Greg Kroah-Hartman
2021-09-09 5:44 ` Joe Perches
2021-09-09 5:52 ` Yu, Lang
2021-09-09 6:07 ` Greg Kroah-Hartman
2021-09-09 6:22 ` Yu, Lang
2021-09-09 6:35 ` Greg Kroah-Hartman
2021-09-09 7:48 ` Yu, Lang
2021-09-09 7:59 ` Greg Kroah-Hartman
2021-09-09 8:48 ` Yu, Lang
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=YTi0xkTVYqUpKXSt@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Lang.Yu@amd.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
/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