From: Mark Brown <broonie@kernel.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Ben Whitten <ben.whitten@gmail.com>,
starnight@g.ncu.edu.tw, hasnain.virk@arm.com,
netdev@vger.kernel.org, liuxuenetmail@gmail.com,
shess@hessware.de, Ben Whitten <ben.whitten@lairdtech.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org, Stefan Rehm <rehm@miromico.ch>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>
Subject: Re: [PATCH v3 lora-next 1/5] regmap: Add regmap_noinc_write API
Date: Thu, 18 Oct 2018 18:18:04 +0100 [thread overview]
Message-ID: <20181018171804.GD25340@sirena.org.uk> (raw)
In-Reply-To: <2908e406-a2e3-29cb-579c-949ddd383e97@suse.de>
[-- Attachment #1: Type: text/plain, Size: 346 bytes --]
On Thu, Oct 18, 2018 at 06:59:52PM +0200, Andreas Färber wrote:
> Mark, please take this one through your tree - I'll rebase the LoRa
> parts on linux-next then.
I don't have a copy of it, if I didn't apply it already and send a pull
request I probably got confused and thought I'd done that already, sorry
- can someone resend please?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-10-18 17:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1539361567-3602-1-git-send-email-ben.whitten@lairdtech.com>
[not found] ` <1539361567-3602-2-git-send-email-ben.whitten@lairdtech.com>
2018-10-18 16:59 ` [PATCH v3 lora-next 1/5] regmap: Add regmap_noinc_write API Andreas Färber
2018-10-18 17:18 ` Mark Brown [this message]
[not found] ` <1539361567-3602-6-git-send-email-ben.whitten@lairdtech.com>
[not found] ` <a89c7974-672f-e5d0-8022-d2c2f9ffeac0@suse.de>
[not found] ` <d22f1f18-0c93-a537-a439-07363174a03b@suse.de>
2018-12-30 10:55 ` [PATCH v3 lora-next 5/5] net: lora: sx125x sx1301: allow radio to register as a clk provider Andreas Färber
2018-12-31 13:27 ` Andreas Färber
2018-12-31 17:50 ` Mark Brown
2018-12-31 22:56 ` Andreas Färber
2019-01-02 0:44 ` Andreas Färber
2019-01-03 12:37 ` Mark Brown
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=20181018171804.GD25340@sirena.org.uk \
--to=broonie@kernel.org \
--cc=afaerber@suse.de \
--cc=ben.whitten@gmail.com \
--cc=ben.whitten@lairdtech.com \
--cc=gregkh@linuxfoundation.org \
--cc=hasnain.virk@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=liuxuenetmail@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rehm@miromico.ch \
--cc=shess@hessware.de \
--cc=starnight@g.ncu.edu.tw \
/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).