From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [GIT] Pull request: u-boot-clk (22.08.2019)
Date: Mon, 26 Aug 2019 09:57:06 +0200 [thread overview]
Message-ID: <20190826095706.6a64d147@jawa> (raw)
In-Reply-To: <20190824164241.GE26850@bill-the-cat>
Hi Tom,
> On Thu, Aug 22, 2019 at 05:14:57PM +0200, Lukasz Majewski wrote:
>
> > Dear Tom,
> >
> > Please find a PR for u-boot-clk branch:
> >
> > The following changes since commit
> > 753e5385ca6d0fe5b5f5a3a97cc96b0f2469ca94:
>
> Can you please provide at least a summary in the future, if not a tag?
I have prepared a tag with a summary:
https://gitlab.denx.de/u-boot/custodians/u-boot-dfu/-/tags/ccf-pr-22.08
I'm a bit confused if this is the right approach for sending PR after
we have switched to gitlab?
>
> >
> > test/py: Add cmd_memory dependency back to test_mmc_wr (2019-08-22
> > 00:09:58 +0200)
> >
> > are available in the git repository at:
> >
> > https://gitlab.denx.de/u-boot/custodians/u-boot-clk
> >
> > for you to fetch changes up to
> > f62ec5c4bba2556202523b0f48655dacbe90753a:
> >
> > clk: imx: add i.MX8MM clk driver (2019-08-22 00:10:15 +0200)
> >
>
> Applied to u-boot/master, thanks!
>
>
Thanks,
>
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190826/8b92cfd0/attachment.sig>
next prev parent reply other threads:[~2019-08-26 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 15:14 [U-Boot] [GIT] Pull request: u-boot-clk (22.08.2019) Lukasz Majewski
2019-08-24 16:42 ` Tom Rini
2019-08-26 7:57 ` Lukasz Majewski [this message]
2019-08-26 13:35 ` Tom Rini
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=20190826095706.6a64d147@jawa \
--to=lukma@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox