linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Chunfeng Yun <chunfeng.yun@mediatek.com>
To: Felipe Balbi <balbi@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mediatek@lists.infradead.org,
	Matthias Brugger <matthias.bgg@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/7] usb: mtu3: convert to devm_platform_ioremap_resource_byname
Date: Thu, 24 Sep 2020 16:58:21 +0800	[thread overview]
Message-ID: <1600937901.10428.4.camel@mhfsdcap03> (raw)
In-Reply-To: <87tuvnej3o.fsf@kernel.org>

On Thu, 2020-09-24 at 10:20 +0300, Felipe Balbi wrote:
> Chunfeng Yun <chunfeng.yun@mediatek.com> writes:
> 
> > Hi Felip,
> >
> >
> > On Mon, 2020-09-07 at 10:42 +0300, Felipe Balbi wrote:
> >> Hi,
> >> 
> >> Chunfeng Yun <chunfeng.yun@mediatek.com> writes:
> >> > Use devm_platform_ioremap_resource_byname() to simplify code
> >> >
> >> > Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.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*"

> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2020-09-24  9:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22  7:51 [PATCH 1/7] usb: mtu3: convert to devm_platform_ioremap_resource_byname Chunfeng Yun
2020-07-22  7:51 ` [PATCH 2/7] usb: phy: am335x: " Chunfeng Yun
2020-07-22  7:51 ` [PATCH 3/7] usb: cdns3: " Chunfeng Yun
2020-07-22  8:46   ` Peter Chen
2020-07-22  7:51 ` [PATCH 4/7] usb: dwc3: " Chunfeng Yun
2020-07-27 12:55   ` Patrice CHOTARD
2020-07-22  7:51 ` [PATCH 5/7] usb: gadget: r8a66597: " Chunfeng Yun
2020-07-22  7:51 ` [PATCH 6/7] usb: gadget: tegra-xudc: " Chunfeng Yun
2020-07-22  7:51 ` [PATCH 7/7] usb: musb: " Chunfeng Yun
2020-11-12 14:08   ` Geert Uytterhoeven
2020-11-13  8:26     ` Chunfeng Yun
2020-09-07  7:42 ` [PATCH 1/7] usb: mtu3: " Felipe Balbi
2020-09-18  3:38   ` Chunfeng Yun
2020-09-24  7:20     ` Felipe Balbi
2020-09-24  8:58       ` Chunfeng Yun [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=1600937901.10428.4.camel@mhfsdcap03 \
    --to=chunfeng.yun@mediatek.com \
    --cc=balbi@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).