From: Heiko Stuebner <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org
Cc: Joseph Chen <chenjh@rock-chips.com>,
gnurou@gmail.com, linus.walleij@linaro.org,
dmitry.torokhov@gmail.com, huangtao@rock-chips.com,
devicetree@vger.kernel.org, tony.xie@rock-chips.com,
zhangqing@rock-chips.com, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, lgirdwood@gmail.com,
linux-gpio@vger.kernel.org, wdc@rock-chips.com,
broonie@kernel.org, linux-input@vger.kernel.org,
mark.rutland@arm.com, w.egorov@phytec.de
Subject: Re: [PATCH v9 00/12] rk808: Add RK805 support
Date: Wed, 09 Aug 2017 11:35:53 +0200 [thread overview]
Message-ID: <1741653.yAH6rPlhTH@phil> (raw)
In-Reply-To: <1502244643-11712-1-git-send-email-chenjh@rock-chips.com>
Hi Joseph,
Am Mittwoch, 9. August 2017, 10:10:41 CEST schrieb Joseph Chen:
> change in v9:
> PATCH V9 1/12: (1) fix spelling issue: s/Chip/chip/
> (2) add: Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>
> PATCH V9 2/12 ~ 12/12: they are applied and no changes, so I don't resend them.
I don't know Lee's workflow, but I'm not sure that is actually true.
I.e. he added "for his own reference" Acked-for-MFD-by: tags to the
patches, but did not apply them (and therefore you cannot find them on [0])
So I'd think you might need to send everything again?
Heiko
[0] https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git/log/?h=for-mfd-next
next prev parent reply other threads:[~2017-08-09 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 2:10 [PATCH v9 00/12] rk808: Add RK805 support Joseph Chen
2017-08-09 2:10 ` [PATCH v9 01/12] mfd: rk808: fix up the chip id get failed Joseph Chen
2017-08-09 9:35 ` Heiko Stuebner [this message]
2017-08-09 9:43 ` [PATCH v9 00/12] rk808: Add RK805 support Joseph Chen
-- strict thread matches above, loose matches on Subject: below --
2017-08-09 10:04 Joseph Chen
[not found] ` <1502273060-12201-1-git-send-email-chenjh-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-08-15 14:14 ` Heiko Stübner
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=1741653.yAH6rPlhTH@phil \
--to=heiko@sntech.de \
--cc=broonie@kernel.org \
--cc=chenjh@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gnurou@gmail.com \
--cc=huangtao@rock-chips.com \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tony.xie@rock-chips.com \
--cc=w.egorov@phytec.de \
--cc=wdc@rock-chips.com \
--cc=zhangqing@rock-chips.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).