All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <1374254658.5357.19@snotra>

diff --git a/a/1.txt b/N1/1.txt
index 001aafa..1a2a748 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,12 +1,12 @@
 On 07/18/2013 09:19:59 PM, Zhang Haijun-B42677 wrote:
-> 
-> 
+>=20
+>=20
 > Thanks.
-> 
+>=20
 > Regards
 > Haijun.
-> 
-> 
+>=20
+>=20
 > > -----Original Message-----
 > > From: Wood Scott-B07421
 > > Sent: Thursday, July 18, 2013 1:14 AM
@@ -40,25 +40,25 @@ On 07/18/2013 09:19:59 PM, Zhang Haijun-B42677 wrote:
 > > > sdhci_host *host)
 > > >
 > > >  	if (vvn > VENDOR_V_22)
-> > >  		host->quirks &= ~SDHCI_QUIRK_NO_BUSY_IRQ;
+> > >  		host->quirks &=3D ~SDHCI_QUIRK_NO_BUSY_IRQ;
 > > > +
-> > > +	if ((SVR_SOC_VER(svr) == SVR_B4860) ||
-> > > +		(SVR_SOC_VER(svr) == SVR_P5020) ||
-> > > +		(SVR_SOC_VER(svr) == SVR_P5040) ||
-> > > +		(SVR_SOC_VER(svr) == SVR_P4080))
-> > > +		host->quirks |= SDHCI_QUIRK_BROKEN_TIMEOUT_VAL;
+> > > +	if ((SVR_SOC_VER(svr) =3D=3D SVR_B4860) ||
+> > > +		(SVR_SOC_VER(svr) =3D=3D SVR_P5020) ||
+> > > +		(SVR_SOC_VER(svr) =3D=3D SVR_P5040) ||
+> > > +		(SVR_SOC_VER(svr) =3D=3D SVR_P4080))
+> > > +		host->quirks |=3D SDHCI_QUIRK_BROKEN_TIMEOUT_VAL;
 > > >  }
 > >
-> > Please don't line up the continuation lines of the if-condition  
+> > Please don't line up the continuation lines of the if-condition =20
 > with the
 > > if-body.
 > [Haijun Wrote:] I'll correct it.
 > >
-> > Please check variant SoCs as well.  If the bug exists on p4080,  
+> > Please check variant SoCs as well.  If the bug exists on p4080, =20
 > then it
 > > exists on p4040.  Likewise with p5040/p5021, and p5020/p5010.
 > >
-> > Is it present on all revisions of these SoCs?  How about p3041,  
+> > Is it present on all revisions of these SoCs?  How about p3041, =20
 > which is
 > > usually pretty similar to p5020?  p2040/p2041?  Is there an erratum
 > > number for this problem?
@@ -67,19 +67,19 @@ On 07/18/2013 09:19:59 PM, Zhang Haijun-B42677 wrote:
 
 These aren't boards; they're chips.
 
-Please find out for sure which chips are affected, or else we'll have  
-support issues later when someone is using a chip you didn't test  
-with.  And always include the fewer-core variants -- if p4080 is  
+Please find out for sure which chips are affected, or else we'll have =20
+support issues later when someone is using a chip you didn't test =20
+with.  And always include the fewer-core variants -- if p4080 is =20
 affected, then p4040 is affected, and so on as described above.
 
 > No errata number yet,
 
 Will one be coming?
 
-> This quirk only give the host max detecting time value to check  
+> This quirk only give the host max detecting time value to check =20
 > card's response. No
 > impact on performance or other functions.
 
 Does this affect boot time if a card is not present?
 
--Scott
+-Scott=
diff --git a/a/content_digest b/N1/content_digest
index 169ecd5..19da000 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -8,21 +8,21 @@
  "To\0Zhang Haijun-B42677 <B42677@freescale.com>\0"
  "Cc\0Wood Scott-B07421 <B07421@freescale.com>"
   linux-mmc@vger.kernel.org <linux-mmc@vger.kernel.org>
-  linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org>
+  Fleming Andy-AFLEMING <afleming@freescale.com>
   cbouatmailru@gmail.com <cbouatmailru@gmail.com>
   cjb@laptop.org <cjb@laptop.org>
- " Fleming Andy-AFLEMING <afleming@freescale.com>\0"
+ " linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org>\0"
  "\00:1\0"
  "b\0"
  "On 07/18/2013 09:19:59 PM, Zhang Haijun-B42677 wrote:\n"
- "> \n"
- "> \n"
+ ">=20\n"
+ ">=20\n"
  "> Thanks.\n"
- "> \n"
+ ">=20\n"
  "> Regards\n"
  "> Haijun.\n"
- "> \n"
- "> \n"
+ ">=20\n"
+ ">=20\n"
  "> > -----Original Message-----\n"
  "> > From: Wood Scott-B07421\n"
  "> > Sent: Thursday, July 18, 2013 1:14 AM\n"
@@ -56,25 +56,25 @@
  "> > > sdhci_host *host)\n"
  "> > >\n"
  "> > >  \tif (vvn > VENDOR_V_22)\n"
- "> > >  \t\thost->quirks &= ~SDHCI_QUIRK_NO_BUSY_IRQ;\n"
+ "> > >  \t\thost->quirks &=3D ~SDHCI_QUIRK_NO_BUSY_IRQ;\n"
  "> > > +\n"
- "> > > +\tif ((SVR_SOC_VER(svr) == SVR_B4860) ||\n"
- "> > > +\t\t(SVR_SOC_VER(svr) == SVR_P5020) ||\n"
- "> > > +\t\t(SVR_SOC_VER(svr) == SVR_P5040) ||\n"
- "> > > +\t\t(SVR_SOC_VER(svr) == SVR_P4080))\n"
- "> > > +\t\thost->quirks |= SDHCI_QUIRK_BROKEN_TIMEOUT_VAL;\n"
+ "> > > +\tif ((SVR_SOC_VER(svr) =3D=3D SVR_B4860) ||\n"
+ "> > > +\t\t(SVR_SOC_VER(svr) =3D=3D SVR_P5020) ||\n"
+ "> > > +\t\t(SVR_SOC_VER(svr) =3D=3D SVR_P5040) ||\n"
+ "> > > +\t\t(SVR_SOC_VER(svr) =3D=3D SVR_P4080))\n"
+ "> > > +\t\thost->quirks |=3D SDHCI_QUIRK_BROKEN_TIMEOUT_VAL;\n"
  "> > >  }\n"
  "> >\n"
- "> > Please don't line up the continuation lines of the if-condition  \n"
+ "> > Please don't line up the continuation lines of the if-condition =20\n"
  "> with the\n"
  "> > if-body.\n"
  "> [Haijun Wrote:] I'll correct it.\n"
  "> >\n"
- "> > Please check variant SoCs as well.  If the bug exists on p4080,  \n"
+ "> > Please check variant SoCs as well.  If the bug exists on p4080, =20\n"
  "> then it\n"
  "> > exists on p4040.  Likewise with p5040/p5021, and p5020/p5010.\n"
  "> >\n"
- "> > Is it present on all revisions of these SoCs?  How about p3041,  \n"
+ "> > Is it present on all revisions of these SoCs?  How about p3041, =20\n"
  "> which is\n"
  "> > usually pretty similar to p5020?  p2040/p2041?  Is there an erratum\n"
  "> > number for this problem?\n"
@@ -83,21 +83,21 @@
  "\n"
  "These aren't boards; they're chips.\n"
  "\n"
- "Please find out for sure which chips are affected, or else we'll have  \n"
- "support issues later when someone is using a chip you didn't test  \n"
- "with.  And always include the fewer-core variants -- if p4080 is  \n"
+ "Please find out for sure which chips are affected, or else we'll have =20\n"
+ "support issues later when someone is using a chip you didn't test =20\n"
+ "with.  And always include the fewer-core variants -- if p4080 is =20\n"
  "affected, then p4040 is affected, and so on as described above.\n"
  "\n"
  "> No errata number yet,\n"
  "\n"
  "Will one be coming?\n"
  "\n"
- "> This quirk only give the host max detecting time value to check  \n"
+ "> This quirk only give the host max detecting time value to check =20\n"
  "> card's response. No\n"
  "> impact on performance or other functions.\n"
  "\n"
  "Does this affect boot time if a card is not present?\n"
  "\n"
- -Scott
+ -Scott=
 
-30cd1e9761ae7cef1e70ed1a2d8dea912849df5bb2c6eab6d30ebaf2b77496b2
+e0b11dfa4a6101e39548d8c016213df2340c46a70c554de394d8623fbfad70e8

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.