All of lore.kernel.org
 help / color / mirror / Atom feed
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.14.17 patches
Date: Thu, 22 Jan 2015 08:58:16 +0100	[thread overview]
Message-ID: <54C0AD98.2080900@denx.de> (raw)
In-Reply-To: <20150121172006.GF16075@hermes.click-hack.org>

On 21.01.2015 18:20, Gilles Chanteperdrix wrote:
> On Wed, Jan 21, 2015 at 04:05:43PM +0100, Stefan Roese wrote:
>> Xilinx Zynq is already supported in the mainline Xenomai git repository.
>> This patch adds support for the v3.14.17 Linux Kernel with the latest
>> arm-6 i-pipe patch additionally to the already present v3.5 and v3.8
>> support.
>
> It would be nice if Zynq support could be integrated into the
> mainline I-pipe git, is Zynq support still experimental, do people
> still need to use a fork ?

At least for v3.14 it might make sense. The Xilinx git repository has 
quite a lot of patches on top of the kernel.org releases (e.g. v3.14). 
For even newer kernel versions this is most likely not necessary.

>> Signed-off-by: Stefan Roese <sr@denx.de>
>> ---
>> Please note that the arm-6 patch that is referenced in the README
>
> One (the only?) interest of -pre and -post patches is to be able to
> update the I-pipe patch without updating the pre and post patches.
> So, I believe the README should not mention a particular version of
> the I-pipe patch. I would rather say: apply
> ipipe-core-3.1.4.17-arm-*.patch

I was just trying to make things clear here. And also following the 
other examples in the README. I can surely send a v2 patch with your 
recommendation to use the ipipe-core-3.1.4.17-arm-*.patch.

> Maybe you could say that it has been tested with that version, so
> that people realize that it may be broken if they use a later I-pipe
> release, but not mention this particular version in the README.

Okay. I'll send a v2 later today.

> Otherwise, looking at the patches themselves: the pre patch reverts
> smp.c and git.c to the mainline version, and the post patch does not
> update them. It means you revert the changes made to these files by
> the fork you use. Is it OK for you ?

Yes. This is similar to the v3.8 pre and post patches.

Thanks,
Stefan



  reply	other threads:[~2015-01-22  7:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21 15:05 [Xenomai] [PATCH] hal/arm: Add Zynq v3.14.17 patches Stefan Roese
2015-01-21 17:20 ` Gilles Chanteperdrix
2015-01-22  7:58   ` Stefan Roese [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-04-10 15:41 claudio.lorini

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=54C0AD98.2080900@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.