From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] git ptxdist best practices
Date: Wed, 8 Jan 2014 21:43:26 +0100 [thread overview]
Message-ID: <20140108204326.GA14696@falbala> (raw)
In-Reply-To: <CAMwGMjxLoDFKoQNiXQq2TuQyqGgzKJexTitNnhrrefJNPOv0Nw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 727 bytes --]
Hei Jon,
On Wed, Jan 08, 2014 at 12:56:37PM -0500, Jon Ringle wrote:
> How do you deal with creating a rule/kernel.make file that does this if I
> build Linux using my own tag? It seems that kernel may need some special
> handling
We use a vanilla kernel and just compile some additional modules for
our own hardware. I can check tomorrow, how this is done, but as far
as I remember just a simple additional make rule.
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-01-08 20:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 2:32 Jon Ringle
2014-01-08 5:56 ` Alexander Dahl
2014-01-08 6:12 ` Jon Ringle
2014-01-08 9:21 ` Alexander Dahl
2014-01-08 9:48 ` Alexander Dahl
2014-01-08 9:52 ` Jürgen Beisert
2014-01-08 17:56 ` Jon Ringle
2014-01-08 20:43 ` Alexander Dahl [this message]
2014-01-08 7:59 ` Jürgen Beisert
2014-01-08 14:14 ` Jon Ringle
2014-01-09 8:10 ` Jürgen Beisert
2014-01-09 9:03 ` Olbrich, Michael
2014-01-09 15:23 ` Jon Ringle
2014-01-09 16:06 ` Michael Olbrich
2014-01-09 16:37 ` Jon Ringle
2014-01-10 15:37 ` Michael Olbrich
2014-01-10 15:41 ` Jon Ringle
2014-01-11 1:47 ` Jon Ringle
2014-01-24 9:21 ` Michael Olbrich
2014-01-24 13:10 ` Jon Ringle
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=20140108204326.GA14696@falbala \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.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