From: Leo Liang <ycliang@andestech.com>
To: u-boot@lists.denx.de
Subject: [PATCH] Revert "riscv: cpu: fu740: clear feature disable CSR"
Date: Tue, 18 May 2021 19:59:55 +0800 [thread overview]
Message-ID: <20210518115939.GA32611@andestech.com> (raw)
In-Reply-To: <CAEUhbmUdH=_Lc-kABEqga0Xm8OkNsVQzB56r4kh=SCFUO00hMg@mail.gmail.com>
On Tue, May 18, 2021 at 05:56:08PM +0800, Bin Meng wrote:
> Hi Green,
>
> On Tue, May 18, 2021 at 5:43 PM Green Wan <green.wan@sifive.com> wrote:
> >
> >
> >
> > On Tue, May 18, 2021 at 3:45 PM Bin Meng <bmeng.cn@gmail.com> wrote:
> >>
> >> Hi Green,
> >>
> >> On Tue, May 18, 2021 at 3:38 PM Leo Liang <ycliang@andestech.com> wrote:
> >> >
> >> > On Fri, May 14, 2021 at 11:45:30AM +0800, Green Wan wrote:
> >> > > Hi Bin,
> >> > >
> >> > > Thanks, I'll include that revert. Just traced back the git log. My original
> >> > > patch is based on fu740. I guess it was merged to fu540 since fu740 series
> >> > > wasn't present yet.
> >> > >
> >> > > Hi Rick,
> >> > >
> >> > > Not sure whether you'll pick fu740 series soon or if any parts need more
> >> > > revisement. Do you prefer that I append both this revert and "disable CSR"
> >> > > patch to fu740&unmatched patch series? If so, I will create v9 patch and
> >> > > include these 2 patches.
> >> > >
> >> > > Or if you prefer to keep them separate from fu740 series, we can wait for
> >> > > fu740&unmatche patch merge and I'll create a separate patch for this revert
> >> > > and CSR disable.
> >> > >
> >> > > What do you think? Many thanks.
> >> > >
> >> > > Regards,
> >> > > - Green
> >> > >
> >> >
> >> > Hi Green,
> >> >
> >> > Could you please append the "disable CSR" patch to fu740 unmatched patch
> >> > and send a v9 patch ? Thanks!
> >> >
> >>
> >> I think you will need some update per this patch as well:
> >> http://patchwork.ozlabs.org/project/uboot/patch/20210511120412.25065-1-bmeng.cn at gmail.com/
> >
> >
> > Hi Bin
> > I updated the change to [patch v9 1/8]. Thanks,
> >
> >>
> >>
> >>
> >> Hi Leo,
> >>
> >> What's your plan for the binman patch series?
> >>
> >> If the binman patch series go first, Green needs to update Unmatched
> >> to use binman as well.
> >
> >
> > Hi Leo/Bin,
> >
> > Are we referring to https://lists.denx.de/pipermail/u-boot/2021-May/448885.html?
>
> This one: http://patchwork.ozlabs.org/project/uboot/list/?series=242992
>
> > I'd prefer to have a separated patch work to track binman changes. Thanks,
>
> Actually that's why I asked Leo the plan. If your patch go before my
> patch, then I will need to do an additional patch to convert
> unmatched.
>
> But if mine go first before yours, you will have to respin another
> version to do the convert in the first place.
>
> Leo, please let us know your plan.
>
Hi Bin/Green,
I was thinking picking Bin's patch first,
because Green's patch could not pass CI.
(Due to some format warning being treated as error
when compiling drivers/pci/pcie_dw_common.c)
At the meantime, we should come up with some fixes to pass CI.
Then Green could send his patch with binman,
or a seperate patch to track binman utility.
What do you guys think?
Best regards,
Leo
> Regards,
> Bin
next prev parent reply other threads:[~2021-05-18 11:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 9:08 [PATCH] Revert "riscv: cpu: fu740: clear feature disable CSR" Bin Meng
2021-05-12 6:39 ` Leo Liang
2021-05-12 13:01 ` Bin Meng
2021-05-12 15:13 ` Green Wan
2021-05-12 15:28 ` Bin Meng
2021-05-14 3:45 ` Green Wan
2021-05-14 3:50 ` Bin Meng
[not found] ` <752D002CFF5D0F4FA35C0100F1D73F3FE5EA22D2@ATCPCS12.andestech.com>
2021-05-14 5:31 ` Rick Chen
2021-05-18 7:38 ` Leo Liang
2021-05-18 7:45 ` Bin Meng
2021-05-18 9:43 ` Green Wan
2021-05-18 9:56 ` Bin Meng
2021-05-18 11:59 ` Leo Liang [this message]
2021-05-18 13:12 ` Green Wan
2021-05-18 14:35 ` Green Wan
2021-05-19 7:52 ` Green Wan
2021-05-19 8:57 ` Leo Liang
2021-05-19 11:09 ` Green Wan
2021-05-19 12:18 ` Bin Meng
2021-05-18 8:10 ` Green Wan
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=20210518115939.GA32611@andestech.com \
--to=ycliang@andestech.com \
--cc=u-boot@lists.denx.de \
/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.