From: nils.faerber@kernelconcepts.de (Nils Faerber)
To: linux-arm-kernel@lists.infradead.org
Subject: New Kirkwood board support
Date: Thu, 28 Oct 2010 21:36:03 +0200 [thread overview]
Message-ID: <4CC9D0A3.70204@kernelconcepts.de> (raw)
In-Reply-To: <20101028190133.GC31158@pengutronix.de>
Hello!
OK, next try ;)
This time with the changes Uwe suggested and without defconfig.
Cheers
nils
--
kernel concepts GbR Tel: +49-271-771091-12
Sieghuetter Hauptweg 48 Fax: +49-271-771091-19
D-57072 Siegen Mob: +49-176-21024535
http://www.kernelconcepts.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tk71-2.6.36.patch
Type: text/x-patch
Size: 5258 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20101028/664c5f93/attachment.bin>
next prev parent reply other threads:[~2010-10-28 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 18:34 New Kirkwood board support Nils Faerber
2010-10-28 19:01 ` Uwe Kleine-König
2010-10-28 19:33 ` Nils Faerber
2010-10-28 19:50 ` Uwe Kleine-König
2010-10-28 19:36 ` Nils Faerber [this message]
2010-10-28 19:43 ` Russell King - ARM Linux
2010-10-28 19:56 ` Nils Faerber
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=4CC9D0A3.70204@kernelconcepts.de \
--to=nils.faerber@kernelconcepts.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).