[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJhGHyCsypVP7VgsNKdQ=rn0hqiJOzSS9p_OGio6k-S2idaLtA@mail.gmail.com>
Date: Mon, 1 Jul 2024 10:51:32 +0800
From: Lai Jiangshan <jiangshanlai@...il.com>
To: Bart Van Assche <bvanassche@....org>
Cc: Tejun Heo <tj@...nel.org>, "Martin K . Petersen" <martin.petersen@...cle.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 01/53] workqueue: Introduce the create*_workqueue2() macros
Hello
On Mon, Jul 1, 2024 at 6:29 AM Bart Van Assche <bvanassche@....org> wrote:
> --- a/include/linux/workqueue.h
> +++ b/include/linux/workqueue.h
> @@ -525,11 +525,20 @@ alloc_workqueue(const char *fmt, unsigned int flags, int max_active, ...);
>
> #define create_workqueue(name) \
> alloc_workqueue("%s", __WQ_LEGACY | WQ_MEM_RECLAIM, 1, (name))
> +#define create_workqueue2(fmt, args...) \
> + alloc_workqueue(fmt, __WQ_LEGACY | WQ_MEM_RECLAIM, 1, ##args)
> #define create_freezable_workqueue(name) \
> alloc_workqueue("%s", __WQ_LEGACY | WQ_FREEZABLE | WQ_UNBOUND | \
> WQ_MEM_RECLAIM, 1, (name))
Is there any possible preprocessor hack to avoid the renaming of the functions?
Thanks
Lai
Powered by blists - more mailing lists