From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] DEVELOPERS: add Yann E. Morin as contact for nanopi_neo_defconfig
Date: Tue, 13 Aug 2019 14:28:02 +0200 [thread overview]
Message-ID: <20190813142802.5a12ce47@windsurf.home> (raw)
In-Reply-To: <20190811134521.GA29186@scaer>
Hello Yann,
On Sun, 11 Aug 2019 15:45:21 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> TBH, your patch even had me wondering where mines were lying around... I
> was able to excavate one out of the junkyard. I am still unsure I can
> make it boot again.
>
> But it is indeed lagging behind in terms of kernel and uboot versions,
> so I can try and rescucitate it.
We don't need an update for this particular board right now: it is
building fine at the moment. My long list of DEVELOPERS patches was
just an attempt of making sure we have one contact for every defconfig
in the tree.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-08-13 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-11 12:07 [Buildroot] [PATCH] DEVELOPERS: add Yann E. Morin as contact for nanopi_neo_defconfig Thomas Petazzoni
2019-08-11 13:45 ` Yann E. MORIN
2019-08-13 12:28 ` Thomas Petazzoni [this message]
2019-08-11 20:06 ` Thomas Petazzoni
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=20190813142802.5a12ce47@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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