On 09/22/2016 06:36 PM, Con Kolivas wrote:
Announcing the latest release of the -ck patchset for improved responsiveness
and interactivity.
https://urldefense.proofpoint.com/v2/url?u=http-3A__ck.kolivas.org_patches_4.0_4.7_4.7-2Dck5_&d=DQIFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=cK1a7KivzZRh1fKQMjSm2A&m=F
Announcing the latest release of the -ck patchset for improved responsiveness
and interactivity.
http://ck.kolivas.org/patches/4.0/4.7/4.7-ck5/
This is normally just a branded version of BFS with some different default
kernel options, however this version incorporates Jens Axboe's writeback
th
This is to announce an updated stable version of the Brain Fuck Scheduler,
version 0.502 for the current stable linux kernel.
http://ck.kolivas.org/patches/bfs/4.0/4.7/4.7-sched-bfs-502.patch
All patches available here:
http://ck.kolivas.org/patches
Code blog:
http://ck-hack.blogspot.com
I wa
Hi! Here is my eight regression report for Linux 4.7. It lists 13
regressions I'm currently aware of. 6 of them are new; none were fixed.
As usual: Please let me know about any regressions missing on the list
or if it contains something which shouldn't be there. Since the release
of
Hi Thorsten,
the ext4 problem reported here https://lkml.org/lkml/2016/8/5/150 an here
https://lkml.org/lkml/2016/8/3/262 seems to me to be a regression, partly,
because my laptop with 4.7.0 was also hit by it but I didn't dug into it.
There seems to be a remedy https://lkml.org/lkml/2016/8/5/367
Hi! Here is my seventh regression report for Linux 4.7. It lists 9
regressions I'm currently aware of. 4 of them are new; 2 are stalled
until the reporter provides more feedback.
The report also mentions 3 regressions that were fixed since the last
report. There is also 1 I plan to remove be
On Monday, August 01, 2016 09:41:53 PM Thorsten Leemhuis wrote:
> In case anyone wonders if I regret doing regression tracking for Linux
> 4.7: No, that is not the case. It isn't really fun, but well, I didn't
> expect it to be ;-) But FWIW, find below a few thoughts about the
In case anyone wonders if I regret doing regression tracking for Linux
4.7: No, that is not the case. It isn't really fun, but well, I didn't
expect it to be ;-) But FWIW, find below a few thoughts about the whole
regression tracking thing I thought might be good to write down and
share
of calculation for digest
Laurent Pinchart (1):
[media] adv7604: Don't ignore pad number in subdev DV timings
pad operations
Linus Torvalds (1):
Linux 4.7
Lionel Landwerlin (1):
drm/i915: add missing condition for committing planes on crtc
Liping Zhang (2):
netfilter:
Hi! Here is my sixth regression report for Linux 4.7. It lists 8
regressions I'm currently aware of; 2 of them are new.
The report also mentions 3 regressions that were fixed since the last
report(¹). There were a few ones that were reported to me in the past
week (many thx for that!) and
> >
> > Updating to 1.6.0 of makedumpfile didn't help. :(
> >
>
> Does anyone else have suggestions on how to debug this? From my original
> post, the dump kernel just reboots and I'm not sure why. Where can I add
> printks to gather more info on why the dump kernel gives on on the dump?
Seems
Ok, so legacy gamma table updates are completely broken for Intel on
Linux-4.7-rc7, the final release candidate.
The good news is that applying Lionel's patch
"drm/i915: add missing condition for committing planes on crtc"
from
https://patchwork.freedesktop.org/patch/89111/
> > >> Also what's the content of your /etc/kdump.conf file?
> > >>
> > >
> > > #raw /dev/sda5
> > > #ext4 /dev/sda3
> > > #ext4 LABEL=/boot
> > > #ext4 UUID=03138356-5e61-4ab3-b58e-27507ac41937
> > > #net my.server.com:/export/tmp
> > > #net u...@my.server.com
> > > path /var/crash
> > > #ext4 /de
there the code in
intel_display.c didn't receive any updates since 13 days and looks like
the broken code from rc6 which according to my testing doesn't work.
So i'd assume legacy gamma table updates are broken in Linux 4.7 final
rc atm. Couldn't test, because for some weir
Cheers,
-
Lionel
On 12/07/16 11:33, Mario Kleiner wrote:
Updating legacy gamma tables, e.g., via RandR doesn't work at all
as of Linux 4.7-rc6.
Reason seems to be that the required call to
drm_atomic_helper_commit_planes_on_crtc is skipped in
intel_atomic_commit after userspace set n
, the final rc afaik?
thanks,
-mario
Cheers,
-
Lionel
On 12/07/16 11:33, Mario Kleiner wrote:
Updating legacy gamma tables, e.g., via RandR doesn't work at all
as of Linux 4.7-rc6.
Reason seems to be that the required call to
drm_atomic_helper_commit_planes_on_crtc is skipped in
intel_ato
:33, Mario Kleiner wrote:
Updating legacy gamma tables, e.g., via RandR doesn't work at all
as of Linux 4.7-rc6.
Reason seems to be that the required call to
drm_atomic_helper_commit_planes_on_crtc is skipped in
intel_atomic_commit after userspace set new gamma tables,
because neither crtc-&
Updating legacy gamma tables, e.g., via RandR doesn't work at all
as of Linux 4.7-rc6.
Reason seems to be that the required call to
drm_atomic_helper_commit_planes_on_crtc is skipped in
intel_atomic_commit after userspace set new gamma tables,
because neither crtc->state->planes_
he Calgary IOMMU entry
Josh Poimboeuf (1):
perf/x86: Fix 32-bit perf user callgraph collection
Julia Lawall (1):
ecryptfs: drop null test before destroy functions
Kuninori Morimoto (1):
ASoC: rsnd: open 31bit of SSICKR mask
Linus Torvalds (1):
Linux 4.7-rc7
Linus Walleij (1):
Hi! Here is my fifth regression report for Linux 4.7. It lists 10
regressions I'm currently aware of; 2 of them are new; 1 of those
seems to be a a side effect of a fix for another regression.
The report also mentions 3 regression that I removed from the list, as
it looks like those issue
e
may be shared
phy: phy-stih407-usb: Inform the reset framework that our reset
line may be shared
phy: miphy28lp: Inform the reset framework that our reset line
may be shared
phy: phy-stih407-usb: Use explicit reset_control_get_exclusive() API
usb: dwc3: st: Use explicit
Hi! Here is my fourth regression report for Linux 4.7; a day earlier then usual.
It has 14 entries;
* 2 of them are new
* 9 regressions (not included here) were fixed since the last report(¹)
* 1 made it to the list after last Sunday (thx for telling me about it Kalle!),
but was fixed before
Thorsten Leemhuis writes:
> Hi! Here is my third regression report for Linux 4.7. It has
> 24 entries; 9 of them are new; 4 regressions (not included here)
> were fixed since the last report(¹).
>
> Please let me know if a regression is missing in the list; or if
> there i
x86: avoid avoid passing around 'thread_info' in stack dumping code
Clarify naming of thread info/stack allocators
x86: fix up a few misc stack pointer vs thread_info confusions
fix up initial thread stack pointer vs thread_info confusion
Linux 4.7-rc5
Lin
Hi! Here is my third regression report for Linux 4.7. It has
24 entries; 9 of them are new; 4 regressions (not included here)
were fixed since the last report(¹).
Please let me know if a regression is missing in the list; or if
there is something on the list which shouldn't be there.
HT
> >> Also what's the content of your /etc/kdump.conf file?
> >>
> >
> > #raw /dev/sda5
> > #ext4 /dev/sda3
> > #ext4 LABEL=/boot
> > #ext4 UUID=03138356-5e61-4ab3-b58e-27507ac41937
> > #net my.server.com:/export/tmp
> > #net u...@my.server.com
> > path /var/crash
> > #ext4 /dev/nvme0n1
> > core_col
On 24.06.2016 18:12, Steve Wise wrote:
>
>> -Original Message-
>> From: nborisov [mailto:n.borisov.l...@gmail.com]
>> Sent: Friday, June 24, 2016 10:07 AM
>> To: Steve Wise; linux-kernel@vger.kernel.org
>> Subject: Re: vmcore not getting created on linux
> -Original Message-
> From: nborisov [mailto:n.borisov.l...@gmail.com]
> Sent: Friday, June 24, 2016 10:07 AM
> To: Steve Wise; linux-kernel@vger.kernel.org
> Subject: Re: vmcore not getting created on linux-4.7
>
>
>
> On 24.06.2016 17:45, Steve Wise wro
On 24.06.2016 17:45, Steve Wise wrote:
> I've been trying to get crash dumps working on linux-4.7 and haven't
> succeeded.
> The kdump kernel boots up and appears to be chugging along and then just
> reboots
> and never creates the vmcore, and fails to create the
I've been trying to get crash dumps working on linux-4.7 and haven't succeeded.
The kdump kernel boots up and appears to be chugging along and then just reboots
and never creates the vmcore, and fails to create the vmcore-dmesg.txt, though
I've never seen that working on my nodes
common: Fix old comment about qualifier descriptor
Lee Jones (1):
ARM: dts: STi: stih407-family: Disable reserved-memory co-processor nodes
Linus Torvalds (1):
Linux 4.7-rc4
Linus Walleij (5):
iio: light: bh1780: return after write
iio: bh1780: dereference the client properly
Hi!
> On 29.05.2016 19:00, Linus Torvalds wrote:
> > [???] Anyway, enough blathering. Go out and test. [???]
>
> And if you find any regressions in 4.7 pre-releases let me know via
> regressi...@leemhuis.info I'll try to compile them into a list and post
> it on LKML once a week similar to how Ra
Linus,
The following changes since commit af8c34ce6ae32addda3788d54a7e340cad22516b:
Linux 4.7-rc2 (2016-06-05 14:31:26 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes up to
030 +0100
--- linux-4.7-rc3/drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.c 2016-06-15
10:58:25.401942157 +0100
***
*** 542,548
struct msm_drm_private *priv = dev->dev_private;
struct drm_crtc *crtc;
! if (pipe < 0 || pipe >= priv->num_crtcs) {
DRM_ERROR(&quo
> -Original Message-
> From: David Binderman [mailto:linuxdev.baldr...@gmail.com]
> Sent: Monday, June 13, 2016 4:16 AM
> To: Deucher, Alexander; Koenig, Christian; airl...@linux.ie; dri-
> de...@lists.freedesktop.org; linux-kernel@vger.kernel.org;
> dcb...@hotmail.com
&g
Hello there,
1.
linux-4.7-rc3/drivers/net/wireless/ath/ath9k/htc_drv_main.c:798]:
(warning) Comparison of a boolean expression with an integer other
than 0 or 1.
Source code is
if (common->ani.caldone <= 0) {
but
drivers/net/wireless/ath/ath.h:bool caldone;
Maybe better code
yup, looks like we can drop the two pipe<0 checks. Care to send a patch?
BR,
-R
On Mon, Jun 13, 2016 at 10:51 AM, David Binderman
wrote:
> Hello there,
>
> 1.
>
> linux-4.7-rc3/drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.c:545]: (style)
> Checking if unsigned variable &#x
Hello there,
1.
linux-4.7-rc3/drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.c:545]: (style)
Checking if unsigned variable 'pipe' is less than zero.
Source code is
if (pipe < 0 || pipe >= priv->num_crtcs) {
2.
linux-4.7-rc3/drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.c:567]:
Hello there,
linux-4.7-rc3/drivers/dma/cppi41.c:509]: (style) Condition 'num>0' is
always false
Source code is
BUG_ON(num > 0);
Local variable num doesn't get used anywhere. Suggest remove.
Regards
David Binderman
Hello there,
linux-4.7-rc3/drivers/gpu/drm/amd/amdgpu/gfx_v7_0.c:4836]: (style)
Boolean result is used in bitwise operation. Clarify expression with
parentheses.
Source code is
if ((ring->me == me_id) & (ring->pipe == pipe_id))
Maybe better code
if ((ring-&g
cheduling while atomic error from commit 49f86ec21c01
Leon Romanovsky (1):
IB/hfi1: Avoid large frame size warning
Linus Torvalds (1):
Linux 4.7-rc3
Linus Walleij (2):
gpio: include in gpiolib-of
gpio: select ANON_INODES
Liu Bo (3):
Btrfs: clear uptodate flags of
On 06/07/2016 11:30, Alexandre Belloni wrote:
> Hi,
>
> On 07/06/2016 at 16:18:31 +0100, David Binderman wrote :
>> Hello there,
>>
[snip]
>> Duplicate. Also in the same file:
>>
>> [drivers/rtc/rtc-ds1685.c:265]: (style) Variable 'ctrlb' is assigned a
>> value that is never used.
This looks li
Hello there,
1.
linux-4.7-rc2/drivers/video/fbdev/sis/init.c:358]: (style) Redundant
condition: If 'LCDwidth >= 800', the comparison 'LCDwidth >= 600' is
always true.
Source code is
if((!(VBFlags & CRT1_LCDA)) || ((LCDwidth >= 800) && (LCDwidt
Hi,
On 07/06/2016 at 16:18:31 +0100, David Binderman wrote :
> Hello there,
>
> 1.
>
> linux-4.7-rc2/drivers/rtc/rtc-ds1685.c:392]: (style) Redundant
> condition: If '!(mday >= 1)', the comparison 'mday <= 31' is always
> true.
>
> S
Hello there,
linux-4.7-rc2/drivers/video/fbdev/intelfb/intelfbdrv.c:1041]: (style)
Redundant condition: If 'msrc > 1', the comparison 'msrc' is always
true.
Source code is
if (msrc && msrc > 1) {
Maybe better code
if (msrc > 1) {
Regards
David Binderman
Hello there,
1.
linux-4.7-rc2/drivers/rtc/rtc-ds1685.c:392]: (style) Redundant
condition: If '!(mday >= 1)', the comparison 'mday <= 31' is always
true.
Source code is
if (!(mday >= 1) && (mday <= 31))
Maybe better code
if (!((mday >= 1) &
David Binderman writes:
> Hello there,
>
> linux-4.7-rc2/drivers/net/wireless/ath/ath6kl/wmi.c:2547]: (style)
> Redundant condition: If 'EXPR <= 7', the comparison 'EXPR < 8' is
> always true.
>
> Source code is
>
> if (!((params-&
Hello there,
linux-4.7-rc2/drivers/net/wireless/ath/ath6kl/wmi.c:2547]: (style)
Redundant condition: If 'EXPR <= 7', the comparison 'EXPR < 8' is
always true.
Source code is
if (!((params->user_pri < 8) &&
(params->user_pri <= 0x7)
Hello there,
linux-4.7-rc2/drivers/net/fjes/fjes_main.c:1346]: (style) Redundant
condition: !is_shared. 'is_shared && (!is_shared || !stop_req_done)'
is equivalent to 'is_shared && !stop_req_done'
Source code is
if ((!stop_req ||
Hello there,
linux-4.7-rc2/drivers/net/ethernet/freescale/fman/fman.c:2329]:
(style) Redundant condition: fman.state.port_mfl[mac_id]. '!A || (A &&
B)' is equivalent to '!A || B'
Source code is
if ((!fman->state->port_mfl[mac_id]) ||
(fman->st
fer the setting of __oprofile_cpu_pmu
drivers/perf: arm_pmu: Avoid leaking pmu->irq_affinity on error
Linus Torvalds (1):
Linux 4.7-rc2
Linus Walleij (5):
gpio: flush direction status in gpiochip_lock_as_irq()
pinctrl: nomadik: fix inversion of gpio direction
gpi
On 29.05.2016 19:00, Linus Torvalds wrote:
> […] Anyway, enough blathering. Go out and test. […]
And if you find any regressions in 4.7 pre-releases let me know via
regressi...@leemhuis.info I'll try to compile them into a list and post
it on LKML once a week similar to how Rafael did it until a f
Hi all,
I have been a bit remiss in publishing these stats and maybe that has
lead to the current lower result for commits in linux-next before the
merge window opened ...
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-201
On Sun, May 29, 2016 at 10:00:25AM -0700, Linus Torvalds wrote:
> Anyway, enough blathering. Go out and test. And in particular, if
> you're a low-level filesystem person, or involved in other ways in
> path component lookup (security layer etc), go check that everything
> looks ok, and if your fi
Usually I close the merge window on a Sunday afternoon, but I've been
known to be annoyed with stragglers and close things a day early. This
time, to spice things up, I decided to just release on Sunday morning
instead.
[ And yes, before you ask , my life really is boring if this is
"spicing thing
On Fri, May 27, 2016 at 5:17 PM, Boris Ostrovsky
wrote:
>
> It does fix it.
Ok, I've committed that in my tree, will do my usual build test and push out.
> This is not the first time we've hit this and people have always been
> changing code to initialize fields in execution path (and I didn't f
- torva...@linux-foundation.org wrote:
> On Fri, May 27, 2016 at 10:14 AM, Boris Ostrovsky
> wrote:
> >
> > This breaks on older compilers:
> >
> > CC fs/nfs/nfs4state.o
> > /home/build/linux-linus/fs/nfs/nfs4state.c:69: error: unknown field
> > ‘data’ specified in initializer
>
> Do
On Fri, May 27, 2016 at 10:14 AM, Boris Ostrovsky
wrote:
>
> This breaks on older compilers:
>
> CC fs/nfs/nfs4state.o
> /home/build/linux-linus/fs/nfs/nfs4state.c:69: error: unknown field
> ‘data’ specified in initializer
Does the attached patch fix it for you?
I don't have easy access t
On 05/26/2016 11:29 AM, Anna Schumaker wrote:
> Hi Linus,
>
> The following changes since commit 44549e8f5eea4e0a41b487b63e616cb089922b99:
>
> Linux 4.6-rc7 (2016-05-08 14:38:32 -0700)
>
> are available in the git repository at:
>
> git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-f
Hi Linus,
The following changes since commit 44549e8f5eea4e0a41b487b63e616cb089922b99:
Linux 4.6-rc7 (2016-05-08 14:38:32 -0700)
are available in the git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-4.7-1
for you to fetch changes up to c7d73af2d249f0323f5
Just one trivial patch for UniPhier (ASOC-32).
Masahiro Yamada (1):
ARM: dts: uniphier: add NAND pinmux node
arch/arm/boot/dts/uniphier-pinctrl.dtsi | 5 +
1 file changed, 5 insertions(+)
--
1.9.1
Masahiro Yamada (2):
arm64: dts: uniphier: fix I2C nodes of PH1-LD20
arm64: dts: uniphier: change release address of spin-table
.../boot/dts/socionext/uniphier-ph1-ld20-ref.dts | 1 -
.../boot/dts/socionext/uniphier-ph1-ld20.dtsi | 28 +++---
2 files changed, 9 insert
Hi Arnd, Olof
Two patches for UniPhier SMP updates.
Please get them into ASOC.
Masahiro Yamada (2):
ARM: uniphier: fix up cache ops broadcast of ACTLR
ARM: uniphier: initialize outer cache for secondary CPUs
arch/arm/include/asm/hardware/cache-uniphier.h | 5 +
arch/arm/mach-uniphie
63 matches
Mail list logo
