All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Avery <tavery321@gmail.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs/core/rtw_mlme_ext.c: Replace yield() call with cond_resched
Date: Thu, 22 Mar 2018 17:16:49 +0000	[thread overview]
Message-ID: <20180322171649.GA28191@kroah.com> (raw)
In-Reply-To: <20180320214541.cknrcuercnhfrx2a@debian>

On Tue, Mar 20, 2018 at 05:45:41PM -0400, Thomas Avery wrote:
> Remove yield() call, yield() does not guarantee progress, and should not
> be used. Cond_resched() is a safer alternative
> 
> Signed-off-by: Thomas Avery <tavery321@gmail.com>
> ---
>  drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

You sent me 3 patches in 2 days with almost the same subject for the
same driver.  Please resend them as a patch series so I know what order
to apply them in.

Also, always use scripts/get_maintainer.pl to find the proper people and
mailing lists to cc:

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Avery <tavery321@gmail.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs/core/rtw_mlme_ext.c: Replace yield() call with cond_resched
Date: Thu, 22 Mar 2018 18:16:49 +0100	[thread overview]
Message-ID: <20180322171649.GA28191@kroah.com> (raw)
In-Reply-To: <20180320214541.cknrcuercnhfrx2a@debian>

On Tue, Mar 20, 2018 at 05:45:41PM -0400, Thomas Avery wrote:
> Remove yield() call, yield() does not guarantee progress, and should not
> be used. Cond_resched() is a safer alternative
> 
> Signed-off-by: Thomas Avery <tavery321@gmail.com>
> ---
>  drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

You sent me 3 patches in 2 days with almost the same subject for the
same driver.  Please resend them as a patch series so I know what order
to apply them in.

Also, always use scripts/get_maintainer.pl to find the proper people and
mailing lists to cc:

thanks,

greg k-h

  reply	other threads:[~2018-03-22 17:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 21:45 [PATCH] staging: rtl8723bs/core/rtw_mlme_ext.c: Replace yield() call with cond_resched Thomas Avery
2018-03-20 21:45 ` Thomas Avery
2018-03-22 17:16 ` Greg KH [this message]
2018-03-22 17:16   ` Greg KH

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=20180322171649.GA28191@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tavery321@gmail.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.