From: Larry Finger <Larry.Finger@lwfinger.net>
To: ByeoungWook Kim <quddnr145@gmail.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
devel@driverdev.osuosl.org,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] rtlwifi: Change long delays to sleeps
Date: Sat, 20 Feb 2016 08:06:59 -0600 [thread overview]
Message-ID: <56C87303.6070203@lwfinger.net> (raw)
In-Reply-To: <CAOxTRzpvnQdb8Wf4M=y4eBM+X-Ey0Y4u=o9X_MMyzTkWQpS=TQ@mail.gmail.com>
On 02/19/2016 11:48 PM, ByeoungWook Kim wrote:
> 2016-02-16 7:12 GMT+09:00 Larry Finger <Larry.Finger@lwfinger.net>:
>> Routine rtl_addr_delay() uses delay statements in code that can
>> sleep. To improve system responsiveness, the various delay statements
>> are changed.
>>
>> In addition, routines rtl_rfreg_delay() and rtl_bb_delay() are
>> rewritten to use the code in rtl_addr_delay() for most of their
>> input values.
>>
>> Suggested-by: Byeoungwook Kim <quddnr145@gmail.com>
>> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
>> ---
>
> Why you are using 'Suggested-by:' of me?
> I think to that your commit was included a part of my
> commit(https://patchwork.kernel.org/patch/8197071/).
Your commit was placed in the deferred list of patches. It did lead me to look
at that section and realize that using delays there was a bug, and that it
should be fixed as quickly as possible. That argues against waiting for your
patches to be implemented. I did use some of your changes. How do you think I
should have referenced your material?
Larry
next prev parent reply other threads:[~2016-02-20 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 22:12 [PATCH] rtlwifi: Change long delays to sleeps Larry Finger
2016-02-16 6:17 ` Souptick Joarder
2016-02-16 16:02 ` Larry Finger
2016-02-20 5:48 ` ByeoungWook Kim
2016-02-20 14:06 ` Larry Finger [this message]
2016-02-20 14:29 ` ByeoungWook Kim
2016-03-07 12:13 ` Kalle Valo
2016-06-04 16:40 ` [PATCH] " Jan Kiszka
2016-06-04 16:52 ` Kalle Valo
2016-06-04 20:02 ` Jan Kiszka
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=56C87303.6070203@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quddnr145@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.