From: Kalle Valo <kvalo@codeaurora.org>
To: Mark Brown <broonie@kernel.org>
Cc: Kai-Heng Feng <kai.heng.feng@canonical.com>,
yhchuang@realtek.com, Dejin Zheng <zhengdejin5@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Alexios Zavras <alexios.zavras@intel.com>,
Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] iopoll: Introduce read_poll_timeout_atomic macro
Date: Thu, 23 Apr 2020 18:13:24 +0300 [thread overview]
Message-ID: <875zdqi6az.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20200423144736.GN4808@sirena.org.uk> (Mark Brown's message of "Thu, 23 Apr 2020 15:47:36 +0100")
Mark Brown <broonie@kernel.org> writes:
> On Thu, Apr 23, 2020 at 02:27:02PM +0300, Kalle Valo wrote:
>
>> Oh, ok. As patch 2 goes to my wireless-drivers-next tree would it be ok
>> for everyone if I take this patch as well?
>
> I'd give it a bit longer than usual for people to review but yeah, if
> nobody complains it's probably reasonable.
Yeah, I'll wait for comments. Thanks!
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-04-23 15:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 6:38 [PATCH 1/2] iopoll: Introduce read_poll_timeout_atomic macro Kai-Heng Feng
2020-04-23 6:38 ` [PATCH 2/2] rtw88: Use udelay instead of usleep in atomic context Kai-Heng Feng
2020-04-23 6:49 ` Kalle Valo
2020-04-23 6:53 ` Kai-Heng Feng
2020-04-23 7:01 ` Kalle Valo
2020-04-23 7:30 ` [PATCH v2 " Kai-Heng Feng
2020-04-23 16:07 ` Kalle Valo
2020-05-06 8:31 ` Kalle Valo
2020-04-23 6:47 ` [PATCH 1/2] iopoll: Introduce read_poll_timeout_atomic macro Kalle Valo
2020-04-23 10:23 ` Mark Brown
2020-04-23 11:27 ` Kalle Valo
2020-04-23 14:47 ` Mark Brown
2020-04-23 15:13 ` Kalle Valo [this message]
2020-04-24 18:49 ` [PATCH v2 " Kai-Heng Feng
2020-05-06 8:30 ` Kalle Valo
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=875zdqi6az.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=alexios.zavras@intel.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=tglx@linutronix.de \
--cc=yhchuang@realtek.com \
--cc=zhengdejin5@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.