[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1600937901.10428.4.camel@mhfsdcap03>
Date: Thu, 24 Sep 2020 16:58:21 +0800
From: Chunfeng Yun <chunfeng.yun@...iatek.com>
To: Felipe Balbi <balbi@...nel.org>
CC: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Matthias Brugger <matthias.bgg@...il.com>,
<linux-usb@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>
Subject: Re: [PATCH 1/7] usb: mtu3: convert to
devm_platform_ioremap_resource_byname
On Thu, 2020-09-24 at 10:20 +0300, Felipe Balbi wrote:
> Chunfeng Yun <chunfeng.yun@...iatek.com> writes:
>
> > Hi Felip,
> >
> >
> > On Mon, 2020-09-07 at 10:42 +0300, Felipe Balbi wrote:
> >> Hi,
> >>
> >> Chunfeng Yun <chunfeng.yun@...iatek.com> writes:
> >> > Use devm_platform_ioremap_resource_byname() to simplify code
> >> >
> >> > Signed-off-by: Chunfeng Yun <chunfeng.yun@...iatek.com>
> >>
> >> why is it so that your patches always come base64 encoded? They look
> >> fine on the email client, but when I try to pipe the message to git am
> >> it always gives me a lot of trouble and I have to manually decode the
> >> body of your messages and recombine with the patch.
> >>
> >> Can you try to send your patches as actual plain text without encoding
> >> the body with base64?
> > Missed the email.
> >
> > Sorry for inconvenience!
> > Is only the commit message base64 encoded, or includes the codes?
>
> The entire thing :-)
I checked my gitconfig, use the default encoding, that is 8bit. if you
still encounter the issue when apply the series patch
https://patchwork.kernel.org/patch/11764953/
I'll resend them by "git send-email --transfer-encoding=8bit 00*"
>
Powered by blists - more mailing lists