From: Wolfram Sang <wsa@kernel.org>
To: "Jonas Mark (BT-FIR/ENG1-Grb)" <Mark.Jonas@de.bosch.com>
Cc: Adam Thomson <Adam.Thomson.Opensource@diasemi.com>,
Support Opensource <Support.Opensource@diasemi.com>,
Lee Jones <lee.jones@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
Steve Twiss <stwiss.opensource@diasemi.com>,
"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
"RUAN Tingquan (BT-FIR/ENG1-Zhu)" <Tingquan.Ruan@cn.bosch.com>,
"Streidl Hubert (BT-FIR/ENG1-Grb)" <Hubert.Streidl@de.bosch.com>
Subject: Re: [PATCH v4] mfd: da9063: Support SMBus and I2C mode
Date: Sat, 20 Feb 2021 12:07:18 +0100 [thread overview]
Message-ID: <20210220110718.GA953@ninjato> (raw)
In-Reply-To: <90bd35fa8c6f420fb1656c678c016509@de.bosch.com>
[-- Attachment #1: Type: text/plain, Size: 307 bytes --]
> Is the patch already on the way upstream?
Can't really speak for Lee here, but during the merge window patches are
usually not applied. So, in something like 2 weeks, usually collecting
for the next cycle begins. Looking at the CC list, I think you added all
the relevant people, so it seems all good.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-02-20 11:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 15:27 [PATCH v4] mfd: da9063: Support SMBus and I2C mode Mark Jonas
2021-02-09 10:40 ` Wolfram Sang
2021-02-09 13:18 ` Adam Thomson
2021-02-19 16:39 ` AW: " Jonas Mark (BT-FIR/ENG1-Grb)
2021-02-20 11:07 ` Wolfram Sang [this message]
2021-02-22 9:10 ` Lee Jones
2021-03-08 14:42 ` Lee Jones
2021-03-09 8:19 ` Mark Jonas
2021-03-09 9:42 ` Lee Jones
2021-03-09 22:42 ` Adam Ward
2021-03-10 8:58 ` Lee Jones
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=20210220110718.GA953@ninjato \
--to=wsa@kernel.org \
--cc=Adam.Thomson.Opensource@diasemi.com \
--cc=Hubert.Streidl@de.bosch.com \
--cc=Mark.Jonas@de.bosch.com \
--cc=Support.Opensource@diasemi.com \
--cc=Tingquan.Ruan@cn.bosch.com \
--cc=lee.jones@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=stwiss.opensource@diasemi.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.