From: Kunwu Chan <chentao@kylinos.cn>
To: Jiri Pirko <jiri@resnulli.us>
Cc: dhowells@redhat.com, marc.dionne@auristor.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux-afs@lists.infradead.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] rxrpc: Simplify the allocation of slab caches
Date: Fri, 2 Feb 2024 17:46:33 +0800 [thread overview]
Message-ID: <961cc4ad-0133-44ee-be22-ba2fbf4ebe12@kylinos.cn> (raw)
In-Reply-To: <1706866812511330.14.seg@mailgw>
On 2024/2/1 20:47, Jiri Pirko wrote:
> Thu, Feb 01, 2024 at 11:09:24AM CET, chentao@kylinos.cn wrote:
>> Use the new KMEM_CACHE() macro instead of direct kmem_cache_create
>> to simplify the creation of SLAB caches.
>>
>> Signed-off-by: Kunwu Chan <chentao@kylinos.cn>
>
> Reviewed-by: Jiri Pirko <jiri@nvidia.com>
>
> btw, why don't you bulk these changes into patchsets of 15 patches? Or,
> given the low complexicity of the patch, just merge multiple patches
> that are changing similar locations togeter.
Sorry, I haven't sent a patchset, I'm worried about messing up.
I'll try to deal with these similar issues in the way you recommended in
the future, thank you for the reminder.
--
Thanks,
Kunwu
next prev parent reply other threads:[~2024-02-02 9:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 10:09 [PATCH net-next] rxrpc: Simplify the allocation of slab caches Kunwu Chan
2024-02-01 12:47 ` Jiri Pirko
2024-02-01 15:38 ` [net-next] " Markus Elfring
[not found] ` <1706866812511330.14.seg@mailgw>
2024-02-02 9:46 ` Kunwu Chan [this message]
2024-02-02 10:28 ` [PATCH net-next] " Jiri Pirko
2024-02-04 3:00 ` Kunwu Chan
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=961cc4ad-0133-44ee-be22-ba2fbf4ebe12@kylinos.cn \
--to=chentao@kylinos.cn \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.