From: Martin Michlmayr <tbm@cyrius.com>
To: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: Cobalt build error
Date: Sat, 8 Mar 2008 08:44:13 +0100 [thread overview]
Message-ID: <20080308074413.GA2581@deprecation.cyrius.com> (raw)
In-Reply-To: <20080308091947.4dc7a756.yoichi_yuasa@tripeaks.co.jp>
* Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp> [2008-03-08 09:19]:
> > Maybe some Cobalt hacker can sort out these issues in the latest kernel.
> > I could try to fix the build but don't have any Cobalt kit for testing ...
>
> I already sent the patch to Dmitry Torokhov.
> He said I will apply it.
> But, it has not been applied yet.
That was quite a while ago, wasn't it? Maybe you could ping him again
or ask Ralf or Andrew to send the patch to Linus.
--
Martin Michlmayr
http://www.cyrius.com/
next prev parent reply other threads:[~2008-03-08 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 15:32 Cobalt build error Ralf Baechle
2008-03-08 0:19 ` Yoichi Yuasa
2008-03-08 7:44 ` Martin Michlmayr [this message]
2008-03-08 8:45 ` [PATCH] Input: fix cobalt_btns loadable keymaps support Yoichi Yuasa
2008-03-08 0:28 ` Cobalt build error Thomas Bogendoerfer
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=20080308074413.GA2581@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=yoichi_yuasa@tripeaks.co.jp \
/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