From: "Mikael Starvik" <mikael.starvik@axis.com>
To: "'Adrian Bunk'" <bunk@stusta.de>,
"Mikael Starvik" <mikael.starvik@axis.com>
Cc: "dev-etrax" <dev-etrax@axis.com>, <linux-kernel@vger.kernel.org>
Subject: RE: cris port lacks a merge?
Date: Mon, 30 Jul 2007 09:44:19 +0200 [thread overview]
Message-ID: <BFECAF9E178F144FAEF2BF4CE739C668030B5C6F@exmail1.se.axis.com> (raw)
In-Reply-To: <BFECAF9E178F144FAEF2BF4CE739C66804AE23FB@exmail1.se.axis.com>
I will make another try soon.
The problem is that every time I try the following happens:
1. I download the bleeding edge latest stuff that you can get
2. I prepare and submit patches
3. I get replies with comments on my patches
4. I fix the patches.
5. I get told that the patches are against a too old version
6. Repeat from 1.
But I will continue to start making attempts to send patches upstreams
again.
Patches are also available at http://developer.axis.com
/Mikael
-----Original Message-----
From: Adrian Bunk [mailto:bunk@stusta.de]
Sent: Sunday, July 15, 2007 2:04 PM
To: Mikael Starvik
Cc: dev-etrax; linux-kernel@vger.kernel.org
Subject: cris port lacks a merge?
Hi Mikael,
the last maintainer update to arch/cris/ was two years ago and it seems
code like e.g. the config variable ETRAX_ARCH_V32 is missing.
I assume there is there some external tree you use that contains updates?
If yes, can you submit the changes for inclusion into the upstream kernel?
TIA
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next parent reply other threads:[~2007-07-30 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BFECAF9E178F144FAEF2BF4CE739C66804AE23FB@exmail1.se.axis.com>
2007-07-30 7:44 ` Mikael Starvik [this message]
2007-07-30 10:51 ` Adrian Bunk
2007-07-30 19:08 ` Roland Dreier
2007-07-15 12:04 Adrian Bunk
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=BFECAF9E178F144FAEF2BF4CE739C668030B5C6F@exmail1.se.axis.com \
--to=mikael.starvik@axis.com \
--cc=bunk@stusta.de \
--cc=dev-etrax@axis.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®