All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Pintu Kumar <pintu.ping@gmail.com>
Cc: "Xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Kernel oops during rtnet loopback usage on x86_64 (e1000e)
Date: Thu, 26 Apr 2018 18:23:05 +0200	[thread overview]
Message-ID: <73a5c9f6-5014-5113-1ddd-2fcf974273bb@siemens.com> (raw)
In-Reply-To: <CAOuPNLiE-Fy3LJrozgsLE9ga0ibC+GOSHO6ciJppU_bnZtbx0g@mail.gmail.com>

On 2018-04-25 13:36, Pintu Kumar wrote:
> Dear Jan,
> 
> Thank you so much for your reply.
> I will try the latest stable version to check again.
> Is ipipe patches (linux: 4.9.51) also needs to be upgraded for this
> issue? Or only xenomai-3/kernel patches are enough?

This particular issue was addressed in the Xenomai core, not the I-pipe
patch.

> 
> Actually, now I am stuck with another question.
> Hope if you could help me.
> 
> As I said, I applied xenomai-3.0.6, kernel patches (using
> prepare_kernel script) to my x86_64 kernel, around 4 months back.
> I am using it since then. After that I never upgraded any patches.
> 
> Now my concern is, how do I apply/upgrade only the latest patches?
> I did not remember the last commit until which I applied the patches.
> 
> Is prepare_kernel script in intelligent enough to find the patch
> difference, and apply on the latest patches ?
> 
> Normally how you people upgrade to the latest xenomai patches.
> If you have any suggestions, please guide me.

Well, best practice is versioning control and build automation. You can
pull the patch into your local kernel or use the i-pipe kernel git tree
as feed (if you have no own patches). Then you just need
prepare-kernel.sh to refresh the xenomai core.

And building everything can also be automated by scripts or more
advanced systems that also track the source revisions for you. Can be
git, can be something like yocto, buildroot etc.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux


  reply	other threads:[~2018-04-26 16:23 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-25  8:39 [Xenomai] Kernel oops during rtnet loopback usage on x86_64 (e1000e) Pintu Kumar
2018-04-25 10:05 ` Jan Kiszka
2018-04-25 11:36   ` Pintu Kumar
2018-04-26 16:23     ` Jan Kiszka [this message]
2018-06-19 13:48       ` Pintu Kumar
2018-06-20  7:54         ` Pintu Kumar
2018-06-21 11:20           ` Pintu Kumar
2018-06-21 11:55             ` Jan Kiszka
2018-06-21 12:27               ` [Xenomai] Kernel panic during kernel bootup on arm64 qemu (e1000e) gengdongjiu
2018-06-21 13:47                 ` Greg Gallagher
2018-06-21 13:56                   ` [Xenomai] Kernel panic during kernel bootup on arm64 qemu gengdongjiu
     [not found]                   ` <5b2baebc.1c69fb81.af598.ef46SMTPIN_ADDED_BROKEN@mx.google.com>
2018-06-21 14:04                     ` Greg Gallagher
2018-06-21 14:14                       ` gengdongjiu
2018-06-21 13:41               ` [Xenomai] Kernel oops during rtnet loopback usage on x86_64 (e1000e) Jan Kiszka
2018-06-21 14:57                 ` Jan Kiszka
2018-06-25 12:56                   ` Pintu Kumar
2018-06-26 11:08                     ` Pintu Kumar
2018-06-27 10:20                       ` Jan Kiszka
2018-06-27 10:56                         ` Pintu Kumar
2018-06-27 11:14                           ` Jan Kiszka
2018-06-27 14:12                             ` Pintu Kumar
2018-06-27 16:17                               ` Jan Kiszka
2018-06-27 17:13                                 ` Pintu Kumar
2018-06-27 17:17                                   ` Greg Gallagher
2018-06-27 17:29                                     ` Pintu Kumar
2018-06-27 18:10                                       ` Philippe Gerum
2018-06-28 10:40                                         ` Pintu Kumar
2018-06-28 13:07                                           ` Philippe Gerum
2018-06-27 18:04                                 ` Philippe Gerum
2018-11-04 16:17                   ` Philippe Gerum
2018-11-06 18:57                     ` Jan Kiszka
2018-11-07 10:04                       ` Philippe Gerum
2018-11-07 10:19                         ` Jan Kiszka
2018-11-07 10:31                           ` Philippe Gerum
2018-11-07 11:19                             ` Jan Kiszka
2018-11-07 11:29                               ` Philippe Gerum

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=73a5c9f6-5014-5113-1ddd-2fcf974273bb@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=pintu.ping@gmail.com \
    --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.