From: Al Viro <viro@ZenIV.linux.org.uk>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Felipe Balbi <balbi@ti.com>,
David Cohen <david.a.cohen@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Baolu Lu <baolu.lu@linux.intel.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [̈́PATCHv5 00/12] usb: ulpi bus
Date: Fri, 15 May 2015 13:40:28 +0100 [thread overview]
Message-ID: <20150515124028.GJ7232@ZenIV.linux.org.uk> (raw)
In-Reply-To: <87lhgqyvw7.fsf@nemi.mork.no>
On Fri, May 15, 2015 at 12:31:36PM +0200, Bjørn Mork wrote:
> Heikki Krogerus <heikki.krogerus@linux.intel.com> writes:
>
> > Hi Al,
> >
> >> How did you end up with that in subject lines? "[\u0344PATCH ", that is...
> >
> > I don't see anything like that in the subject lines? Is someone else
> > seeing it?
>
> Your subject lines are properly encoded utf8, starting with:
>
> =?UTF-8?q?=5B=CD=84PATCHv5=2004/12=5D=20
>
> The question is how you ended up using the three byte [̈́ instead of the
> more commonly used [ character? Both look identical on my screen, but I
> guess some email clients might have a problem decoding the first one.
No problem (in UTF8-supporting xterm), just a visible difference, triggering
"huh? how did that happen?" reaction... FWIW, looking at it with xmag now
shows this:
**
** ** **
**** **
******
**
**
**
**
**
**
**
**
**
**
**
******
which is sane enough for [ with this diacritic mark, so the things worked
as they ought to. I'm just curious - what had produced that in the subject
lines of this thread in the first place?
prev parent reply other threads:[~2015-05-15 12:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 12:26 [̈́PATCHv5 00/12] usb: ulpi bus Heikki Krogerus
2015-05-13 12:26 ` [̈́PATCHv5 01/12] usb: add bus type for USB ULPI Heikki Krogerus
2015-05-13 12:26 ` [̈́PATCHv5 02/12] usb: dwc3: USB2 PHY register access bits Heikki Krogerus
2015-05-13 12:26 ` [̈́PATCHv5 03/12] usb: dwc3: ULPI or UTMI+ select Heikki Krogerus
2015-05-13 12:26 ` [̈́PATCHv5 04/12] usb: dwc3: store driver data earlier Heikki Krogerus
2015-05-13 12:26 ` [̈́PATCHv5 05/12] usb: dwc3: cache hwparams earlier Heikki Krogerus
2015-05-13 12:26 ` [̈́PATCHv5 06/12] usb: dwc3: soft reset to it's own function Heikki Krogerus
2015-05-13 12:26 ` [̈́PATCHv5 07/12] usb: dwc3: setup phys earlier Heikki Krogerus
2015-05-13 12:26 ` [̈́PATCHv5 08/12] usb: dwc3: add hsphy_interface property Heikki Krogerus
2015-05-13 12:26 ` [̈́PATCHv5 09/12] usb: dwc3: pci: add quirk for Baytrails Heikki Krogerus
2015-05-13 12:26 ` [̈́PATCHv5 10/12] usb: dwc3: add ULPI interface support Heikki Krogerus
2015-05-13 12:26 ` [̈́PATCHv5 11/12] phy: helpers for USB ULPI PHY registering Heikki Krogerus
2015-05-13 12:26 ` [̈́PATCHv5 12/12] phy: add driver for TI TUSB1210 ULPI PHY Heikki Krogerus
2015-05-13 14:22 ` [̈́PATCHv5 00/12] usb: ulpi bus Al Viro
2015-05-15 7:09 ` Heikki Krogerus
2015-05-15 7:39 ` Tal Shorer
2015-05-15 10:31 ` Bjørn Mork
2015-05-15 12:03 ` Jeff Epler
2015-05-15 12:40 ` Al Viro [this message]
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=20150515124028.GJ7232@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=balbi@ti.com \
--cc=baolu.lu@linux.intel.com \
--cc=bjorn@mork.no \
--cc=david.a.cohen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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.