mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Byungchul Park <byungchul.park@lge.com>
To: <fweisbec@gmail.com>, <peterz@infradead.org>, <mingo@kernel.org>,
	<rostedt@goodmis.org>
Cc: <linux-kernel@vger.kernel.org>, <kernel-team@lge.com>
Subject: Re: [RESEND PATCH] irq_work: Don't reinvent the wheel but use existing llist API
Date: Tue, 30 May 2017 14:29:20 +0900	[thread overview]
Message-ID: <20170530052920.GJ28017@X58A-UD3R> (raw)
In-Reply-To: <1494549935-13972-1-git-send-email-byungchul.park@lge.com>

On Fri, May 12, 2017 at 09:45:35AM +0900, Byungchul Park wrote:
> Although llist provides proper APIs, they are not used. Make them used.

+to peterz@infradead.org
+to mingo@kernel.org
+to rostedt@goodmis.org

I am not sure whom should I send this patch to..
Could you check this if you are right person?

> 
> Signed-off-by: Byungchul Park <byungchul.park@lge.com>
> ---
>  kernel/irq_work.c | 6 +-----
>  1 file changed, 1 insertion(+), 5 deletions(-)
> 
> diff --git a/kernel/irq_work.c b/kernel/irq_work.c
> index bcf107c..e2ebe8c 100644
> --- a/kernel/irq_work.c
> +++ b/kernel/irq_work.c
> @@ -138,11 +138,7 @@ static void irq_work_run_list(struct llist_head *list)
>  		return;
>  
>  	llnode = llist_del_all(list);
> -	while (llnode != NULL) {
> -		work = llist_entry(llnode, struct irq_work, llnode);
> -
> -		llnode = llist_next(llnode);
> -
> +	llist_for_each_entry(work, llnode, llnode) {
>  		/*
>  		 * Clear the PENDING bit, after this point the @work
>  		 * can be re-used.
> -- 
> 1.9.1

  reply	other threads:[~2017-05-30  5:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12  0:45 Byungchul Park
2017-05-30  5:29 ` Byungchul Park [this message]
2017-05-31 14:04   ` Frederic Weisbecker
2017-06-01  7:29     ` Byungchul Park
2017-09-05  2:38     ` Byungchul Park
2017-09-27  0:00     ` Byungchul Park
2017-10-18  5:11     ` Byungchul Park
2017-10-25  5:51     ` Byungchul Park

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=20170530052920.GJ28017@X58A-UD3R \
    --to=byungchul.park@lge.com \
    --cc=fweisbec@gmail.com \
    --cc=kernel-team@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.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

Powered by JetHome