On Mon, May 18, 2020 at 3:48 PM Don Zickus wrote:
> Hi Javier,
>
> We update the fedora kernel process to use a git tree to submit patches
> now.
>
This was a request for stable, which doesn't follow this process. Javier
asked before he sent it here. It has been added and included in the
From: Don Zickus on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/362#note_344755261
Dropped patch1 because internally Red Hat may drop the whole patch
anyway. Let's just fix the Fedora compile problem for now.
___
kernel
From: Don Zickus
Upstream status: RHEL only
The function rh_check_supported is a RHEL function to limit the
platforms RHEL does not want to support.
To avoid imposing this requirement on Fedora, the function was
wrapped with CONFIG_RHEL_DIFFERENCES so Fedora can disable this.
However, this
On Mon, May 18, 2020 at 04:42:59PM -0400, Don Zickus wrote:
> On Mon, May 18, 2020 at 07:42:26PM -, GitLab Bridge on behalf of
> jeremycline wrote:
> > From: Jeremy Cline
> >
> > There are no static files at this time. I don't know the first thing
> > about CSS and rely on my elders and
Hi Javier,
We update the fedora kernel process to use a git tree to submit patches now.
Can I ask you to spend a few minutes to read over the new steps
https://cki-project.gitlab.io/kernel-ark/submitting-contributions.html
and resubmit your request as a merge request?
Hopefully after the
On Mon, May 18, 2020 at 07:42:26PM -, GitLab Bridge on behalf of
jeremycline wrote:
> From: Jeremy Cline
>
> There are no static files at this time. I don't know the first thing
> about CSS and rely on my elders and betters to make the documentation
> look presentable. Configuring a static
From: Jeremy Cline
There are no static files at this time. I don't know the first thing
about CSS and rely on my elders and betters to make the documentation
look presentable. Configuring a static directory also generates a Sphinx
warning when it isn't present (which it isn't on clean checkouts
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: e94772f8cab7 - [redhat] kernel-5.7.0-0.rc6.1
The results of these automated tests are provided below.
Overall result: PASSED
> > > FYI, I've experienced a stability issue with the jetson-tk1 NIC since
> > > kernel 5.3 and later.
> > > This is reported upstream at
> > > https://bugzilla.kernel.org/show_bug.cgi?id=206217
> > > To sum-up: under some "MMC and network I/O load" (dnf update or scp of
> > > large file), the
On Mon, May 18, 2020 at 5:09 AM Peter Robinson wrote:
>
> > FYI, I've experienced a stability issue with the jetson-tk1 NIC since
> > kernel 5.3 and later.
> > This is reported upstream at
> > https://bugzilla.kernel.org/show_bug.cgi?id=206217
> > To sum-up: under some "MMC and network I/O load"
> FYI, I've experienced a stability issue with the jetson-tk1 NIC since
> kernel 5.3 and later.
> This is reported upstream at
> https://bugzilla.kernel.org/show_bug.cgi?id=206217
> To sum-up: under some "MMC and network I/O load" (dnf update or scp of
> large file), the pciport receives AER
From: Hans de Goede
Before commit cfc4c189bc70 ("pwm: Read initial hardware state at request
time"), a driver's get_state callback would get called once per PWM from
pwmchip_add().
pwm-lpss' runtime-pm code was relying on this, getting a runtime-pm ref for
PWMs which are enabled at probe time
Hi there,
FYI, I've experienced a stability issue with the jetson-tk1 NIC since
kernel 5.3 and later.
This is reported upstream at https://bugzilla.kernel.org/show_bug.cgi?id=206217
To sum-up: under some "MMC and network I/O load" (dnf update or scp of
large file), the pciport receives AER
13 matches
Mail list logo
