From: Cristi Magherusan <Cristi.Magherusan@net.utcluj.ro>
To: buildroot@busybox.net
Subject: [Buildroot] obtaining linux kernel from git
Date: Wed, 19 May 2010 00:02:41 +0300 [thread overview]
Message-ID: <1274216561.7985.1.camel@ufo> (raw)
In-Reply-To: <4B4C4897.7000400@carallon.com>
On Tue, 2010-01-12 at 10:01 +0000, William Wagner wrote:
> On 11/01/2010 21:50, Grant Likely wrote:
> > I posted a patch doing this a while ago, but I didn't pursue it and it
> > didn't get merged.
> >
> > http://lists.busybox.net/pipermail/buildroot/2008-October/023215.html
> >
> >
> The patch looks great. The only thing I think could be improved is
> setting BR2_LINUX26_VERSION. Need this so that BR2_PACKAGE_LINUX_KCONFIG
> gets set to something sensible (default is
> $(BR2_BOARD_PATH)/$(BR2_BOARD_NAME)-linux-$(BR2_LINUX26_VERSION).config).
>
> Not sure what it would be best to set BR2_LINUX26_VERSION to, could just
> be "git" although if you specify a different branch I think that might
> be better
>
> Will resubmit some patches once I'm done.
>
> Will
Hi,
Any news about this?
I'm interested in this feature and I would really like to see it merged.
What else needs to be done in order to achieve this goal?
Regards,
Cristi
--
Cristi M?gheru?an, alumnus System/Network Engineer
Technical University of Cluj-Napoca, Romania
http://cc.utcluj.ro +40264 401247
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100519/4be282c1/attachment.pgp>
next prev parent reply other threads:[~2010-05-18 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 20:00 [Buildroot] obtaining linux kernel from git William Wagner
2010-01-11 21:50 ` Grant Likely
2010-01-12 1:42 ` Michael S. Zick
2010-01-12 10:01 ` William Wagner
2010-05-18 21:02 ` Cristi Magherusan [this message]
2010-05-20 9:25 ` William Wagner
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=1274216561.7985.1.camel@ufo \
--to=cristi.magherusan@net.utcluj.ro \
--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