All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Jean-Baptiste Trédez" <jean-baptiste.tredez@ba-healthcare.com>,
	xenomai@xenomai.org
Subject: Re: [PATCH] net/drivers: fec: Update fec driver for xenomai 3 + linux kernel 5.10 and add I.MX8 support
Date: Fri, 3 Dec 2021 12:12:26 +0100	[thread overview]
Message-ID: <f27da059-677e-60d7-cd92-ace953b0fdcf@siemens.com> (raw)
In-Reply-To: <9c940d0d-8be1-9a37-4c7c-060a00716ed1@siemens.com>

On 01.12.21 20:04, Jan Kiszka via Xenomai wrote:
> On 26.11.21 09:02, Jean-Baptiste Trédez via Xenomai wrote:
>> Current fec driver does not build on xenomai 3 and on recent kernel (ex : 5.10). Fec driver was completely rewritten on mainline kernel.
>> This work remove old fec driver, port driver from mainline linux 5.10 to xenomai 3.x and add I.MX8 support.
>>
>> Tested on i.MX8Q target
>>
> 
> Thanks for the contribution! I assume you also tested this driver with
> debug options on to catch any potential locking issues (sorry, TL;DR -
> with "R" = "review")?
> 
> Can we also make add this driver to our CI build (.gitlab-ci.yml)? Which
> options need to be on in addition to make it compile?
> 

It turns out that all needed switches were already set - and... the
build fails for 5.4:

https://gitlab.com/Xenomai/xenomai-hacker-space/-/jobs/1846388391

Could you have a look and fix this up?

Also, it looks like we do not build for 4.19
(https://gitlab.com/Xenomai/xenomai-hacker-space/-/jobs/1846388392). If
that kernel had no support for the target SoC, then this is fine, though.

Thanks,
Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux


  reply	other threads:[~2021-12-03 11:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-26  8:02 [PATCH] net/drivers: fec: Update fec driver for xenomai 3 + linux kernel 5.10 and add I.MX8 support Jean-Baptiste Trédez
2021-12-01 19:04 ` Jan Kiszka
2021-12-03 11:12   ` Jan Kiszka [this message]
2021-12-03 11:29     ` Florian Bezdeka
2021-12-07 17:39       ` Jean-Baptiste Tredez

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=f27da059-677e-60d7-cd92-ace953b0fdcf@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=jean-baptiste.tredez@ba-healthcare.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.