From: Stefan Roese <sr@denx.de>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] [PATCH] hal/arm: Add Zynq v3.5.7 patches
Date: Tue, 31 Dec 2013 07:13:34 +0100 [thread overview]
Message-ID: <52C2608E.2030609@denx.de> (raw)
In-Reply-To: <52C1EA3B.2030009@xenomai.org>
On 30.12.2013 22:48, Gilles Chanteperdrix wrote:
> On 12/30/2013 04:15 PM, Stefan Roese wrote:
>> Xilinx Zynq is already supported in the mainline Xenomai git repository.
>> This patch adds support for the v3.5.7 Linux Kernel with the latest
>> arm-6 i-pipe patch additionally to the already present v3.8 support.
>
> Sorry, I can not take these patches:
> - they contain changes in the I-pipe core not related to the Zynq
> architecture, these should be submitted separately as patches to the
> I-pipe git itself;
Okay.
> - they contain changes in the Linux code, not related to Zynq either,
> probably due to a mismatch between the stable revision you are using. In
> order to use a more recent revision, please post a patch modifying the
> I-pipe git to use that more recent stable revision;
Its the other way around. The Xilinx code is based on Linux v3.5. And
the i-pipe patch is based on v3.5.7. So the pre-patch also includes the
move for the xilinx code from v3.5 to v3.5.7.
> - they contain a defconfig file, if you want to make that file
> available, please put it to some ftp or http server somewhere and put
> the URL in the readme;
Okay.
> Really, the pre and post patches should be short, here they are enormous.
Mostly because of the v3.5 -> v3.5.7 move for the Xilinx code. Should I
post this v3.5 -> v3.5.7 diff as a separate patch?
Thanks,
Stefan
next prev parent reply other threads:[~2013-12-31 6:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 15:15 [Xenomai] [PATCH] hal/arm: Add Zynq v3.5.7 patches Stefan Roese
2013-12-30 21:48 ` Gilles Chanteperdrix
2013-12-31 6:13 ` Stefan Roese [this message]
2013-12-31 8:33 ` Gilles Chanteperdrix
2014-01-03 10:24 ` Stefan Roese
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=52C2608E.2030609@denx.de \
--to=sr@denx.de \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.