From: Andrew Lunn <andrew@lunn.ch>
To: Jisheng Zhang <jszhang@marvell.com>
Cc: adrian.hunter@intel.com, huziji@marvell.com,
ulf.hansson@linaro.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mmc: sdhci-xenon: kill xenon_clean_phy()
Date: Wed, 17 May 2017 13:56:02 +0200 [thread overview]
Message-ID: <20170517115602.GD19968@lunn.ch> (raw)
In-Reply-To: <20170517171726.2ede556d@xhacker>
> As pointed out by RMK, the sdhci-xenon driver is merged in current 4.12-rc1,
> so we just need to apply this fix in later rcN.
Yep. It helps the maintainer if you point this out in the patch, after
the ---.
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: sdhci-xenon: kill xenon_clean_phy()
Date: Wed, 17 May 2017 13:56:02 +0200 [thread overview]
Message-ID: <20170517115602.GD19968@lunn.ch> (raw)
In-Reply-To: <20170517171726.2ede556d@xhacker>
> As pointed out by RMK, the sdhci-xenon driver is merged in current 4.12-rc1,
> so we just need to apply this fix in later rcN.
Yep. It helps the maintainer if you point this out in the patch, after
the ---.
Andrew
next prev parent reply other threads:[~2017-05-17 11:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 6:17 [PATCH] mmc: sdhci-xenon: kill xenon_clean_phy() Jisheng Zhang
2017-05-16 6:17 ` Jisheng Zhang
2017-05-16 6:17 ` Jisheng Zhang
2017-05-16 12:22 ` Andrew Lunn
2017-05-16 12:22 ` Andrew Lunn
2017-05-16 12:48 ` Russell King - ARM Linux
2017-05-16 12:48 ` Russell King - ARM Linux
2017-05-17 9:17 ` Jisheng Zhang
2017-05-17 9:17 ` Jisheng Zhang
2017-05-17 9:17 ` Jisheng Zhang
2017-05-17 11:56 ` Andrew Lunn [this message]
2017-05-17 11:56 ` Andrew Lunn
2017-05-17 6:50 ` Hu Ziji
2017-05-17 6:50 ` Hu Ziji
2017-05-17 6:50 ` Hu Ziji
2017-05-17 10:19 ` Adrian Hunter
2017-05-17 10:19 ` Adrian Hunter
2017-05-19 8:30 ` Ulf Hansson
2017-05-19 8:30 ` Ulf Hansson
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=20170517115602.GD19968@lunn.ch \
--to=andrew@lunn.ch \
--cc=adrian.hunter@intel.com \
--cc=huziji@marvell.com \
--cc=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
/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.