All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@nxp.com>
To: u-boot@lists.denx.de
Subject: Please pull NXP i.MX nxp-imx-20200422
Date: Mon, 27 Apr 2020 01:24:50 +0000	[thread overview]
Message-ID: <DB6PR0402MB2760F6966A1FA5915315BF9E88AF0@DB6PR0402MB2760.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CAOMZO5ACr+5P79T7SY9ec3cFnaMUR_qidtJzW7e_Dr1hJmf_Mg@mail.gmail.com>

> Subject: Re: Please pull NXP i.MX nxp-imx-20200422
> 
> Hi Peng,
> 
> On Wed, Apr 22, 2020 at 10:54 AM Peng Fan <peng.fan@nxp.com> wrote:
> >
> > Hi Stefano,
> >
> > Please pull this version nxp-imx-20200422, with patches sent out to ML.
> > Based on yours master branch.
> 
> Series looks good:
> Reviewed-by: Fabio Estevam <festevam@gmail.com>
> 

Thanks for the review.

> Just some comments:
> 
> - Please try sending the patches more often and in small batches as it is easier
> to review rather then a 24 patches series.

ok. I was a bit busy in the past days, not that active.
will keep small patchset in future.

> - The speed grading logic is becoming too complicated and difficult to scale.
> Please improve it in a separate patch if you have a chance.

ok. I'll switch to use is_imx6ulx to replace is_imx6ull.
There will be a conflict with Marek's fec clock part, I'll resend the patchset
based on Marek's patch.

Thanks again.

Peng.

> 
> Thanks

      reply	other threads:[~2020-04-27  1:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22 13:54 Please pull NXP i.MX nxp-imx-20200422 Peng Fan
2020-04-22 15:04 ` Fabio Estevam
2020-04-23  1:35   ` Peng Fan
2020-04-25 14:28 ` Fabio Estevam
2020-04-27  1:24   ` Peng Fan [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=DB6PR0402MB2760F6966A1FA5915315BF9E88AF0@DB6PR0402MB2760.eurprd04.prod.outlook.com \
    --to=peng.fan@nxp.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.