From: Marcin Wojtas <mw@semihalf.com>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: edk2-devel-01 <edk2-devel@lists.01.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
nadavh@marvell.com, Neta Zur Hershkovits <neta@marvell.com>,
Kostya Porotchkin <kostap@marvell.com>,
Hua Jing <jinghua@marvell.com>,
semihalf-dabros-jan <jsd@semihalf.com>
Subject: Re: [platforms: PATCH v3 0/4] Armada 7k/8k - misc improvements pt.3
Date: Tue, 5 Dec 2017 15:16:20 +0100 [thread overview]
Message-ID: <CAPv3WKcK7rkyj-+C6y_AdVoX0P=B_846YdnF+VoPzd5omL7kKQ@mail.gmail.com> (raw)
In-Reply-To: <20171205141033.i5oijhjgc2e6om3e@bivouac.eciton.net>
2017-12-05 15:10 GMT+01:00 Leif Lindholm <leif.lindholm@linaro.org>:
>
> Thanks.
> For the series:
> Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
> Pushed as 84c212b1b4..2348894694.
>
Thanks a lot!
Marcin
>
> On Tue, Dec 05, 2017 at 06:57:01AM +0100, Marcin Wojtas wrote:
> > Hi,
> >
> > The third version of the patchset brings the corrections
> > requested in the review. Details can be found in the changelog
> > below.
> >
> > The patches are available in the github:
> > https://github.com/MarvellEmbeddedProcessors/edk2-open-platform/commits/misc-upstream-r20171205
> >
> > I'm looking forward to your comments or remarks.
> >
> > Best regards,
> > Marcin
> >
> > Changelog:
> > v2 -> v3
> > * 1/4
> > - remove hardcoded DEFINE from the dsc file and enable
> > passing the argument in a command line during build time
> > - Add RB
> >
> > * 3/4
> > - Mention additional help information improvements in the
> > commit log
> >
> > * 4/4
> > - Add RB
> >
> > v1 -> v2
> >
> > * 1/4
> > - Add tftp as a build-time selectable option
> > - Update commit message
> >
> > * 2/4
> > - Add RB
> >
> > * 3/4
> > - Leave initial file format and reword commit message
> >
> > * 4/4
> > - Leave PHY_AUTONEGOTIATE_TIMEOUT unmodified and
> > remove double definition of the timeout.
> >
> > Marcin Wojtas (4):
> > Marvell/Armada: Switch to dynamic tftp command
> > Marvell/Armada: Fix watchdog control base
> > Marvell/Applications: FirmwareUpdate: Fix usage information
> > Marvell/Drivers: MvPhyDxe: Cleanup the header
> >
> > Platform/Marvell/Applications/FirmwareUpdate/FUpdate.uni | Bin 5146 -> 5190 bytes
> > Platform/Marvell/Armada/Armada.dsc.inc | 6 +-
> > Platform/Marvell/Armada/Armada70x0.fdf | 3 +
> > Platform/Marvell/Drivers/Net/Phy/MvPhyDxe/MvPhyDxe.c | 2 +-
> > Platform/Marvell/Drivers/Net/Phy/MvPhyDxe/MvPhyDxe.h | 152 ++++----------------
> > 5 files changed, 39 insertions(+), 124 deletions(-)
> >
> > --
> > 2.7.4
> >
prev parent reply other threads:[~2017-12-05 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 5:57 [platforms: PATCH v3 0/4] Armada 7k/8k - misc improvements pt.3 Marcin Wojtas
2017-12-05 5:57 ` [platforms: PATCH v3 1/4] Marvell/Armada: Switch to dynamic tftp command Marcin Wojtas
2017-12-05 5:57 ` [platforms: PATCH v3 2/4] Marvell/Armada: Fix watchdog control base Marcin Wojtas
2017-12-05 5:57 ` [platforms: PATCH v3 3/4] Marvell/Applications: FirmwareUpdate: Fix usage information Marcin Wojtas
2017-12-05 5:57 ` [platforms: PATCH v3 4/4] Marvell/Drivers: MvPhyDxe: Cleanup the header Marcin Wojtas
2017-12-05 14:10 ` [platforms: PATCH v3 0/4] Armada 7k/8k - misc improvements pt.3 Leif Lindholm
2017-12-05 14:16 ` Marcin Wojtas [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-list 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='CAPv3WKcK7rkyj-+C6y_AdVoX0P=B_846YdnF+VoPzd5omL7kKQ@mail.gmail.com' \
--to=devel@edk2.groups.io \
/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