From: Mark Brown <broonie@kernel.org>
To: Kalle Valo <kvalo@codeaurora.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 11:23:47 +0100 [thread overview]
Message-ID: <20200423102347.GC4808@sirena.org.uk> (raw)
In-Reply-To: <87lfmmn1fo.fsf@kamboji.qca.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 380 bytes --]
On Thu, Apr 23, 2020 at 09:47:23AM +0300, Kalle Valo wrote:
> I don't know who maintains iopoll.h, at least MAINTAINERS file doesn't
> have an entry, so not sure how to handle this patch.
Andrew Moton often picks up things like that, or if it's used by some
other patch as the original message indicated then often whoever picks
up the user can pick up the core change as well.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-04-23 10:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200423063811.2636-1-kai.heng.feng@canonical.com>
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 [this message]
2020-04-23 11:27 ` Kalle Valo
2020-04-23 14:47 ` Mark Brown
2020-04-23 15:13 ` Kalle Valo
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=20200423102347.GC4808@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexios.zavras@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=kai.heng.feng@canonical.com \
--cc=kvalo@codeaurora.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).