From: Helge Deller <deller@gmx.de>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Carlos O'Donell <carlos@systemhalted.org>,
a.beregalov@gmail.com, linux-parisc@vger.kernel.org
Subject: Re: can't compile kernel for parisc
Date: Sat, 28 Feb 2009 01:04:04 +0100 [thread overview]
Message-ID: <49A87F74.8040700@gmx.de> (raw)
In-Reply-To: <20090227164630.642474EF8@hiauly1.hia.nrc.ca>
John David Anglin wrote:
> I was hoping to try Helge's recent changes but I don't think they
> are in Kyle's parisc tree.
All my (important) patches are in Kyle's tree, but you need to
take a look into the "merge" and "parisc" branches of his tree:
http://git.kernel.org/?p=linux/kernel/git/kyle/parisc-2.6.git;a=shortlog;h=merge
http://git.kernel.org/?p=linux/kernel/git/kyle/parisc-2.6.git;a=shortlog;h=parisc
Helge
next prev parent reply other threads:[~2009-02-28 0:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 10:47 can't compile kernel for parisc Alexander Beregalov
2009-02-27 12:24 ` Carlos O'Donell
2009-02-27 13:04 ` Alexander Beregalov
2009-02-27 13:18 ` Carlos O'Donell
2009-02-27 15:40 ` Alexander Beregalov
2009-02-27 15:56 ` Carlos O'Donell
2009-02-27 16:46 ` John David Anglin
2009-02-27 17:55 ` Alexander Beregalov
2009-02-28 16:17 ` John David Anglin
2009-03-02 16:13 ` Alexander Beregalov
2009-03-02 17:20 ` John David Anglin
2009-03-02 18:01 ` Alexander Beregalov
2009-03-02 18:17 ` John David Anglin
2009-03-02 18:28 ` John David Anglin
2009-03-03 12:57 ` Alexander Beregalov
2009-03-03 16:33 ` John David Anglin
2009-03-18 11:55 ` Alexander Beregalov
2009-03-18 14:00 ` John David Anglin
2009-04-02 15:55 ` Kyle McMartin
2009-04-03 13:57 ` Alexander Beregalov
2009-03-20 21:40 ` Grant Grundler
2009-03-21 1:56 ` Alexander Beregalov
2009-04-02 15:52 ` Kyle McMartin
2009-02-28 0:04 ` Helge Deller [this message]
2009-02-27 16:51 ` John David Anglin
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=49A87F74.8040700@gmx.de \
--to=deller@gmx.de \
--cc=a.beregalov@gmail.com \
--cc=carlos@systemhalted.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=linux-parisc@vger.kernel.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