All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamin Lin <jamin_lin@aspeedtech.com>
To: Joel Stanley <joel@jms.id.au>
Cc: Andrew Jeffery <andrew@aj.id.au>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	Troy Lee <troy_lee@aspeedtech.com>,
	Steven Lee <steven_lee@aspeedtech.com>
Subject: Re: u-boot:rsa adds rsa3072 algorithm
Date: Thu, 10 Feb 2022 14:06:50 +0800	[thread overview]
Message-ID: <20220210060649.GA4157@aspeedtech.com> (raw)
In-Reply-To: <CACPK8XeUeDSV7T8Rrtp2G99d0LdyXu0dSzHj3DnwRQr8Sm9zaA@mail.gmail.com>

The 02/07/2022 06:11, Joel Stanley wrote:
> On Mon, 7 Feb 2022 at 02:26, Jamin Lin <jamin_lin@aspeedtech.com> wrote:
> > This patch was applied to u-boot/master, http://patchwork.ozlabs.org/project/uboot/patch/20220119082323.4567-2-jamin_lin@aspeedtech.com/
> >
> > Commit   2a4b0d5890deb0c973f8db7bb03adad96aff1050
> >
> > https://github.com/u-boot/u-boot/commit/2a4b0d5890deb0c973f8db7bb03adad96aff1050
> >
> > Could you please help to backport the patch to the openbmc/u-boot tree?
> 
> This patch doesn't apply cleanly. Can you send a backport to the list?
> Please be sure to test that it applies, builds and runs against the
> v2019.04-aspeed-openbmc tree.
> 
> Cheers,
> 
> Joel

I send the new patch and ready for review.
Thanks-Jamin

      reply	other threads:[~2022-02-10  6:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07  2:26 u-boot:rsa adds rsa3072 algorithm Jamin Lin
2022-02-07  6:02 ` Openbmc u-boot trees (was Re: u-boot:rsa adds rsa3072 algorithm) Joel Stanley
2022-02-07  7:02   ` Jamin Lin
2022-02-09  2:28     ` ChiaWei Wang
2022-02-11  2:11       ` Joel Stanley
2022-02-15  1:47         ` ChiaWei Wang
2022-02-17  3:29         ` Patrick Williams
2022-02-07  6:11 ` u-boot:rsa adds rsa3072 algorithm Joel Stanley
2022-02-10  6:06   ` Jamin Lin [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=20220210060649.GA4157@aspeedtech.com \
    --to=jamin_lin@aspeedtech.com \
    --cc=andrew@aj.id.au \
    --cc=joel@jms.id.au \
    --cc=openbmc@lists.ozlabs.org \
    --cc=steven_lee@aspeedtech.com \
    --cc=troy_lee@aspeedtech.com \
    /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.