From: Greg KH <gregkh@linuxfoundation.org>
To: Longlong Xia <xialonglong1@huawei.com>
Cc: chenwandun@huawei.com, linux-kernel@vger.kernel.org,
rafael@kernel.org, sunnanyong@huawei.com,
wangkefeng.wang@huawei.com
Subject: Re: [PATCH -next 0/3] cleanup of devtmpfs_*_node()
Date: Fri, 10 Feb 2023 09:17:14 +0100 [thread overview]
Message-ID: <Y+X9irDpjtowQEZr@kroah.com> (raw)
In-Reply-To: <20230210073309.4050841-1-xialonglong1@huawei.com>
On Fri, Feb 10, 2023 at 07:33:06AM +0000, Longlong Xia wrote:
> The test steps:
> 1. Set the SElinux label of /dev to user_home_t
> 2. modprobe zram num_devices=1000
>
> The above test result is that there is no zram device was found in the
> /dev. And don't see any errors printed in jouranls/dmesg. Of course,
> it is rare to create 1000 zram devices, use dev_err may be better.
>
> Longlong Xia (3):
> devtmpfs: add debug info to handle()
> driver core: add error handling for devtmpfs_create_node()
> devtmpfs: remove return value of devtmpfs_delete_node()
>
> drivers/base/base.h | 4 ++--
> drivers/base/core.c | 8 ++++++--
> drivers/base/devtmpfs.c | 20 ++++++++++++++------
> 3 files changed, 22 insertions(+), 10 deletions(-)
>
> Best Regards,
> Longlong Xia
This is a v2 series, please mark them as such, saying what changed from
the previous submission. Otherwise our tools get totally confused and I
can not apply them.
Also just send it as a new thread, don't reply to the old one, there's
no need for making it that complex.
thanks,
greg k-h
next prev parent reply other threads:[~2023-02-10 8:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 3:32 [PATCH -next 0/3] cleanup of devtmpfs_*_node() Longlong Xia
2023-02-02 3:32 ` [PATCH -next 1/3] devtmpfs: convert to pr_fmt Longlong Xia
2023-02-02 8:33 ` Greg KH
2023-02-02 3:32 ` [PATCH -next 2/3] devtmpfs: add debug info to handle() Longlong Xia
2023-02-02 8:30 ` Greg KH
2023-02-10 7:33 ` [PATCH -next 0/3] cleanup of devtmpfs_*_node() Longlong Xia
2023-02-10 7:33 ` [PATCH -next 1/3] devtmpfs: add debug info to handle() Longlong Xia
2023-02-10 7:33 ` [PATCH -next 2/3] driver core: add error handling for devtmpfs_create_node() Longlong Xia
2023-02-10 7:33 ` [PATCH -next 3/3] devtmpfs: remove return value of devtmpfs_delete_node() Longlong Xia
2023-02-10 8:17 ` Greg KH [this message]
2023-02-02 3:32 ` [PATCH -next 3/3] devtmpfs: remove return value of devtmpfs_*_node() & devtmpfs_submit_req() Longlong Xia
2023-02-02 8:33 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2023-02-02 3:10 [PATCH -next 0/3] cleanup of devtmpfs_*_node() Longlong Xia
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=Y+X9irDpjtowQEZr@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chenwandun@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sunnanyong@huawei.com \
--cc=wangkefeng.wang@huawei.com \
--cc=xialonglong1@huawei.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