From: "Leif Lindholm" <leif@nuviainc.com>
To: devel@edk2.groups.io, xiewenyi2@huawei.com
Cc: ard.biesheuvel@arm.com, songdongkuang@huawei.com
Subject: Re: [edk2-devel] [PATCH EDK2-non-osi v1 0/1] Silicon/Hisilicon: fix compile issues triggered by VariablePolicy
Date: Tue, 26 Jan 2021 12:44:20 +0000 [thread overview]
Message-ID: <20210126124420.GR1664@vanye> (raw)
In-Reply-To: <5eef10bf-ff62-6236-6501-026484729a63@huawei.com>
Many thanks.
Reviewed-by: Leif Lindholm <leif@nuviainc.com>
Pushed as 04744d2432ba.
On Tue, Jan 12, 2021 at 15:06:21 +0800, wenyi,xie via groups.io wrote:
> Hi Leif,
>
> I have pushed my patch to github, here's the link:
> https://github.com/leadsama/edk2-non-osi/tree/compile_issue_fix_v1
>
> Thanks
> Wenyi
>
> On 2021/1/11 19:50, Leif Lindholm wrote:
> > Hi Xie,
> >
> > If I received such a link without having expressly asked for it, I
> > would have deleted it automatically.
> >
> > Please push, to *any* publicly accessible git repository, a branch
> > containing these patches, and then send me a link to that branch in
> > reply to this email.
> >
> > Best Regards,
> >
> > Leif
> >
> > On Mon, Jan 11, 2021 at 14:36:41 +0800, wenyi,xie via groups.io wrote:
> >> Hi Leif,
> >>
> >> Happy new year.
> >>
> >> For some reason I couldn't push the commit to the github, so I
> >> created the binary files and sent them to a file transfer system,
> >> this system would sent you an email which include the web link to
> >> download binary files, have you ever received the email which
> >> include download link ?(The transfer system only sent email with
> >> downlink to receiver, so I could not see the link and I was not sure
> >> whether you received the email.)
> >>
> >> As the link is only available for two weeks, so I will apply for
> >> another download link again this week.
> >>
> >> Thanks
> >> Wenyi
> >>
> >>
> >> On 2021/1/9 0:50, Leif Lindholm wrote:
> >>> Hi Wenyi,
> >>>
> >>> Apologies for very late response - this arrived just before I left for
> >>> Christmas holidays.
> >>>
> >>> However, could you also include the link to the repository and branch
> >>> I can fetch the commits from?
> >>>
> >>> /
> >>> Leif
> >>>
> >>> On Wed, Dec 16, 2020 at 09:41:06 +0800, Wenyi Xie wrote:
> >>>> Main Changes :
> >>>> Replace binary files to fix compile issue caused by AsciiStrnCpy
> >>>> and UnicodeStrToAsciiStr missing.
> >>>>
> >>>> Wenyi Xie (1):
> >>>> Silicon/Hisilicon: fix compile issues triggered by VariablePolicy
> >>>>
> >>>> Silicon/Hisilicon/Hi1610/Library/Hi1610Serdes/Hi1610SerdesLib.lib | Bin 587188 -> 598188 bytes
> >>>> Silicon/Hisilicon/Hi1616/Library/Hi1616Serdes/Hi1616SerdesLib.lib | Bin 726884 -> 725820 bytes
> >>>> Silicon/Hisilicon/Library/IpmiCmdLib/IpmiCmdLib.lib | Bin 210280 -> 258210 bytes
> >>>> 3 files changed, 0 insertions(+), 0 deletions(-)
> >>>>
> >>>> --
> >>>> 2.20.1.windows.1
> >>>>
> >>> .
> >>>
> >>
> >>
> >>
> >>
> >>
> > .
> >
>
>
>
>
>
prev parent reply other threads:[~2021-01-26 12:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 1:41 [PATCH EDK2-non-osi v1 0/1] Silicon/Hisilicon: fix compile issues triggered by VariablePolicy wenyi,xie
2020-12-16 1:41 ` [PATCH EDK2-non-osi v1 1/1] " wenyi,xie
2021-01-08 16:50 ` [PATCH EDK2-non-osi v1 0/1] " Leif Lindholm
2021-01-11 6:36 ` wenyi,xie
2021-01-11 11:50 ` [edk2-devel] " Leif Lindholm
2021-01-12 7:06 ` wenyi,xie
2021-01-26 12:44 ` Leif Lindholm [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=20210126124420.GR1664@vanye \
--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