On Mon, Aug 05, 2024 at 07:01:09PM +0900, JaeJoon Jung wrote: > Implementation of new Hash Tree [PATCH v2] > ------------------------------------------ > Add spinlock.h and rcupdate.h in the include/linux/htree.h > Add htree_root structue to interface locking. > htree_root.ht_lock is spinlock_t to run spin_lock. > htree_root.ht_first is __rcu type to access rcu API. > Access the kernel standard API using macros. > > full source: > ------------ > https://github.com/kernel-bz/htree.git > > Manual(PDF): > ------------ > https://github.com/kernel-bz/htree/blob/main/docs/htree-20240802.pdf > > Signed-off-by: JaeJoon Jung <rgbi3307@xxxxxxxxx> > --- > include/linux/htree.h | 117 ++++++++++++++++++++++++++- > lib/htree-test.c | 182 ++++++++++++++++++++++-------------------- > lib/htree.c | 29 ++++++- > 3 files changed, 238 insertions(+), 90 deletions(-) Hi, This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree. You are receiving this message because of the following common error(s) as indicated below: - You did not specify a description of why the patch is needed, or possibly, any description at all, in the email body. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/process/submitting-patches.rst for what is needed in order to properly describe the change. - You did not write a descriptive Subject: for the patch, allowing Greg, and everyone else, to know what this patch is all about. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/process/submitting-patches.rst for what a proper Subject: line should look like. If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers. thanks, greg k-h's patch email bot
