linux-kernel - Re: [PATCH v10 3/3] clk: mediatek: add UART0 clock support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <160219350512.310579.18205549684029464732@swboyd.mtv.corp.google.com>
Date:   Thu, 08 Oct 2020 14:45:05 -0700
From:   Stephen Boyd <sboyd@...nel.org>
To:     Hanks Chen <hanks.chen@...iatek.com>
Cc:     Michael Turquette <mturquette@...libre.com>,
        Matthias Brugger <matthias.bgg@...il.com>,
        devicetree@...r.kernel.org, CC Hwang <cc.hwang@...iatek.com>,
        Andy Teng <andy.teng@...iatek.com>,
        Linus Walleij <linus.walleij@...aro.org>,
        YueHaibing <yuehaibing@...wei.com>, linux-kernel@...r.kernel.org,
        linux-clk@...r.kernel.org, linux-gpio@...r.kernel.org,
        Rob Herring <robh+dt@...nel.org>,
        linux-mediatek@...ts.infradead.org,
        Loda Chou <loda.chou@...iatek.com>,
        mtk01761 <wendell.lin@...iatek.com>,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v10 3/3] clk: mediatek: add UART0 clock support

Quoting Hanks Chen (2020-10-07 19:39:13)
> On Wed, 2020-10-07 at 19:00 -0700, Stephen Boyd wrote:
> > Quoting Hanks Chen (2020-10-03 03:06:47)
> > > Hi Michael & Stephen,
> > > 
> > > Please kindly let me know your comments about this patch.
> > > Thanks
> > > 
> > 
> > What's the base for this patch? I tried applying to v5.9-rc1 and it
> > didn't work.
> 
> Sorry, what does that mean?
> 
> Do you have encountered a merged conflict or run time failed?
> 
> I based on kernel-5.8-rc1 to add it and it can boot to kernel shell.
> 

Ah I see what it is. The email isn't actually plain text, it is base64
encoded and so git am gets confused by the CRLF line endings that are
encoded in there. Any chance you can send patches in actual plain text
format in the future?