diff for duplicates of <d6699a26485443bf8a9a798ddca05e6f@ti.com> diff --git a/a/1.txt b/N1/1.txt index 1bfa3c7..a7ae0af 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,20 +1,16 @@ ->=20 +> > >> > >> > pm_runtime handles sdio power on and power off transitions. -> >> > An old workaround for trying to control the power explicitly from th= -e -> >> > driver was in fact causing failures on suspend/resume as the mmc lay= -er +> >> > An old workaround for trying to control the power explicitly from the +> >> > driver was in fact causing failures on suspend/resume as the mmc layer > >> > already power the module on resume. > >> > > >> > In case of resume pm_runtime_get sync returns a positive device's > usage -> >> > count causing the driver to try an re-initialize an already initiali= -zed +> >> > count causing the driver to try an re-initialize an already initialized > >> > device. This was causing sdio bus failure on resume. > >> > -> >> > Remove this manual power on/off sequence as it is in-fact not needed= -. +> >> > Remove this manual power on/off sequence as it is in-fact not needed. > >> > > >> > Signed-off-by: Eyal Reizer <eyalr@ti.com> > >> > Acked-by: Tony Lindgren <tony@atomide.com> @@ -31,11 +27,11 @@ zed > > Yes, this is correct. No change in the actual patch hence there was no > change > > Log. ->=20 +> > _Always_ include a change log, even if you didn't actually change > anything. Otherwise the maintainer has no clue what has changed and why > a new version was submitted. ->=20 +> Understood. Thanks! BR, diff --git a/a/content_digest b/N1/content_digest index 7278b2d..e57ee8b 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -14,23 +14,19 @@ " linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>\0" "\00:1\0" "b\0" - ">=20\n" + "> \n" "> >>\n" "> >> > pm_runtime handles sdio power on and power off transitions.\n" - "> >> > An old workaround for trying to control the power explicitly from th=\n" - "e\n" - "> >> > driver was in fact causing failures on suspend/resume as the mmc lay=\n" - "er\n" + "> >> > An old workaround for trying to control the power explicitly from the\n" + "> >> > driver was in fact causing failures on suspend/resume as the mmc layer\n" "> >> > already power the module on resume.\n" "> >> >\n" "> >> > In case of resume pm_runtime_get sync returns a positive device's\n" "> usage\n" - "> >> > count causing the driver to try an re-initialize an already initiali=\n" - "zed\n" + "> >> > count causing the driver to try an re-initialize an already initialized\n" "> >> > device. This was causing sdio bus failure on resume.\n" "> >> >\n" - "> >> > Remove this manual power on/off sequence as it is in-fact not needed=\n" - ".\n" + "> >> > Remove this manual power on/off sequence as it is in-fact not needed.\n" "> >> >\n" "> >> > Signed-off-by: Eyal Reizer <eyalr@ti.com>\n" "> >> > Acked-by: Tony Lindgren <tony@atomide.com>\n" @@ -47,14 +43,14 @@ "> > Yes, this is correct. No change in the actual patch hence there was no\n" "> change\n" "> > Log.\n" - ">=20\n" + "> \n" "> _Always_ include a change log, even if you didn't actually change\n" "> anything. Otherwise the maintainer has no clue what has changed and why\n" "> a new version was submitted.\n" - ">=20\n" + "> \n" "Understood. Thanks!\n" "\n" "BR,\n" Eyal -d7ac4c1aebbff204c05746fa2ce78220a57919a126317a0bbb5f1bdfc847fea1 +442c467cac3eea8a7016d7861ead500c18ea1ca96966b111549af9768d9af606
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.