From: "Marek Behún" <kabel@kernel.org>
To: u-boot@lists.denx.de
Subject: Please pull u-boot-dm/next into -next
Date: Sun, 21 Mar 2021 00:21:30 +0100 [thread overview]
Message-ID: <20210321002130.562e6bea@kernel.org> (raw)
In-Reply-To: <CAPnjgZ37Q4uXzhgM4eYhY+=hkjysbQ9k_cccD72LE+tEzGvCDQ@mail.gmail.com>
Simon,
you forgot to drop my regmap patch.
Marek
next prev parent reply other threads:[~2021-03-20 23:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 20:58 Please pull u-boot-dm/next into -next Simon Glass
2021-03-20 23:21 ` Marek Behún [this message]
2021-03-21 0:20 ` Simon Glass
2021-03-21 1:16 ` Bin Meng
2021-03-21 1:18 ` Simon Glass
2021-03-21 1:20 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2021-03-26 6:05 Simon Glass
2021-03-26 19:14 ` Tom Rini
2021-01-06 2:53 Simon Glass
2021-01-06 12:56 ` Tom Rini
2020-12-23 19:04 Simon Glass
2020-12-24 14:12 ` Tom Rini
2020-12-14 15:50 Simon Glass
2020-12-15 14:06 ` Tom Rini
2020-12-15 16:28 ` Simon Glass
2020-12-17 2:10 ` Simon Glass
2020-12-17 14:01 ` 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=20210321002130.562e6bea@kernel.org \
--to=kabel@kernel.org \
--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