On 06/13/2014 11:54 AM, Greg KH wrote:
On Fri, Jun 13, 2014 at 09:11:29AM +0800, micky wrote:
On 06/13/2014 01:23 AM, Greg KH wrote:
On Wed, Jun 11, 2014 at 02:56:25PM +0800, micky_ching@xxxxxxxxxxxxxx wrote:
From: Micky Ching <micky_ching@xxxxxxxxxxxxxx>
commit d8ec26d7f8287f5788a494f56e8814210f0e64be upstream
No it is not.
Sorry, I use the ID based on. This patch ID is:
commit 6777c0a182be3dd52ca4b250d9a37849a1061ced
a27fbf2f067b0cd ("mmc: add ignorance case for CMD13 CRC error") produced
a cmd.flags unhandled in realtek pci host driver. This will make MMC
card fail to initialize, this patch is used to handle the new cmd.flags
condition and MMC card can be used.
Cc: <stable@xxxxxxxxxxxxxxx> # 3.13.x
Signed-off-by: Micky Ching <micky_ching@xxxxxxxxxxxxxx>
---
drivers/mmc/host/rtsx_pci_sdmmc.c | 3 +++
1 file changed, 3 insertions(+)
What is the real commit id of this patch, and what stable kernel tree(s)
do you want it applied to?
commit 6777c0a182be3dd52ca4b250d9a37849a1061ced
That commit id is not in Linus's tree. Where are you getting it from?
Have you read Documentation/stable_kernel_rules.txt for how to properly
submit a patch for the stable kernel releases?
commit 5027251eced6e34315a52bd841279df957f627bb
This should be the right commit id.
thanks,
greg k-h
.
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html