From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please pull u-boot-marvell/master (v2)
Date: Fri, 12 Apr 2019 16:45:35 -0400 [thread overview]
Message-ID: <20190412204535.GD4664@bill-the-cat> (raw)
In-Reply-To: <CAFOYHZCf4UWKJ8R7Wx6CW8D1HHTDNZUpC04U_X6wrWh=YfruRg@mail.gmail.com>
On Sat, Apr 13, 2019 at 08:37:46AM +1200, Chris Packham wrote:
> On Fri, 12 Apr 2019, 11:27 PM Stefan Roese, <sr@denx.de> wrote:
>
> > Hi Tom,
> >
> > please pull the following Marvell related patches. I've
> > removed the board support, causing the out-of-tree building
> > error for now. I'll push this one after its resolved.
>
>
> I'll take a look at the db-88f6281 out of tree build failures. I think I've
> got a handle on the issue now. I probably won't have a fix before you go
> offline but it should be waiting for you when you get back. Have a good
> break.
>
> "Check for configs without MAINTAINERS entry". I've not seen
> > this error before. Frankly, I'm in a bit of a hurry, as I am
> > leaving for a 10 days vacation tomorrow and this will be my
> > last try to get these Marvell patches upstream before it.
>
>
> If this is due to one of my recent additions I'll send a fix direct to Tom.
It was a trivial enough problem on
board/Marvell/db-xc3-24g4xg/MAINTAINERS that I fixed it up in the merge.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190412/601464f2/attachment.sig>
next prev parent reply other threads:[~2019-04-12 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 11:27 [U-Boot] Please pull u-boot-marvell/master (v2) Stefan Roese
2019-04-12 20:37 ` Chris Packham
2019-04-12 20:45 ` Tom Rini [this message]
2019-04-13 3:41 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2018-05-17 15:42 Stefan Roese
2018-05-17 20:16 ` 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=20190412204535.GD4664@bill-the-cat \
--to=trini@konsulko.com \
--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