From: pavel@denx.de (Pavel Machek)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Explanation for cip-kernel-config
Date: Sat, 20 Jul 2019 22:24:44 +0200 [thread overview]
Message-ID: <20190720202444.GA10335@amd> (raw)
In-Reply-To: <CAEss1E+TW8udmVVL63OxbPLgndbKW7XiE5bKn1XvgK8J4rfWBQ@mail.gmail.com>
Hi!
> Yup... I am very interested in this one, I should say. ;-)
>
> Let us see what will come out of this effort. :-)
I've commited suitable config for socfpga board. (And added it to the
README).
If you need some kind of help with kernel configuration (etc), just
let me know.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190720/fe0a5817/attachment.sig>
next prev parent reply other threads:[~2019-07-20 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 14:05 [cip-dev] Explanation for cip-kernel-config Pavel Machek
2019-07-19 18:10 ` Zoran S
2019-07-20 20:24 ` Pavel Machek [this message]
2019-07-21 17:56 ` Zoran S
2019-07-21 18:17 ` Pavel Machek
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=20190720202444.GA10335@amd \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.org \
/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