Re: [git pull] drm for 5.14-rc1

2021-09-22 Thread Maxime Ripard
On Mon, Sep 20, 2021 at 10:47:43AM -0700, Linus Torvalds wrote: > On Mon, Sep 20, 2021 at 10:33 AM Maxime Ripard wrote: > > > > What I was interested in was more about the context itself, and I'd > > still like an answer on whether it's ok to wait for a review for 5 > > months though, or if it's

Re: [git pull] drm for 5.14-rc1

2021-09-20 Thread Linus Torvalds
On Mon, Sep 20, 2021 at 10:33 AM Maxime Ripard wrote: > > What I was interested in was more about the context itself, and I'd > still like an answer on whether it's ok to wait for a review for 5 > months though, or if it's an expectation from now on that we are > supposed to fix bugs over the

Re: [git pull] drm for 5.14-rc1

2021-09-20 Thread Maxime Ripard
On Mon, Sep 20, 2021 at 10:10:57AM -0700, Linus Torvalds wrote: > On Mon, Sep 20, 2021 at 5:17 AM Maxime Ripard wrote: > > > > I'm sorry, but I find that situation to be a bit ridiculous. > > Honestly, the original report about the pulseaudio problem came in > over two weeks ago, and all you

Re: [git pull] drm for 5.14-rc1

2021-09-20 Thread Linus Torvalds
On Mon, Sep 20, 2021 at 5:17 AM Maxime Ripard wrote: > > I'm sorry, but I find that situation to be a bit ridiculous. Honestly, the original report about the pulseaudio problem came in over two weeks ago, and all you seemed to do was to ignore everything that Sudip said and reported. THAT is

Re: [git pull] drm for 5.14-rc1

2021-09-20 Thread Sudip Mukherjee
On Mon, Sep 20, 2021 at 1:17 PM Maxime Ripard wrote: > > On Sun, Sep 19, 2021 at 10:19:35AM -0700, Linus Torvalds wrote: > > On Sun, Sep 19, 2021 at 4:05 AM Sudip Mukherjee > > wrote: > > > > > > And indeed, reverting 27da370e0fb3 ("drm/vc4: hdmi: Remove > > > drm_encoder->crtc usage") on top of

Re: [git pull] drm for 5.14-rc1

2021-09-20 Thread Maxime Ripard
On Mon, Sep 20, 2021 at 10:55:31AM +0200, Maxime Ripard wrote: > Hi, > > On Sat, Sep 18, 2021 at 11:18:33AM +0200, Michael Stapelberg wrote: > > torvalds at linux-foundation.org (Linus Torvalds) writes: > > > Did I fix it up correctly? Who knows. The code makes more sense to me > > > now and

Re: [git pull] drm for 5.14-rc1

2021-09-20 Thread Maxime Ripard
On Sun, Sep 19, 2021 at 10:19:35AM -0700, Linus Torvalds wrote: > On Sun, Sep 19, 2021 at 4:05 AM Sudip Mukherjee > wrote: > > > > And indeed, reverting 27da370e0fb3 ("drm/vc4: hdmi: Remove > > drm_encoder->crtc usage") on top of d4d016caa4b8 ("alpha: move > > __udiv_qrnnd library function to

Re: [git pull] drm for 5.14-rc1

2021-09-20 Thread Maxime Ripard
Hi, On Sat, Sep 18, 2021 at 11:18:33AM +0200, Michael Stapelberg wrote: > torvalds at linux-foundation.org (Linus Torvalds) writes: > > Did I fix it up correctly? Who knows. The code makes more sense to me > > now and seems valid. But I really *really* want to stress how locking > > is important.

Re: [git pull] drm for 5.14-rc1

2021-09-19 Thread Linus Torvalds
On Sun, Sep 19, 2021 at 4:05 AM Sudip Mukherjee wrote: > > And indeed, reverting 27da370e0fb3 ("drm/vc4: hdmi: Remove > drm_encoder->crtc usage") on top of d4d016caa4b8 ("alpha: move > __udiv_qrnnd library function to arch/alpha/lib/") > has fixed the error. Ok, since your pulseaudio problem was

Re: [git pull] drm for 5.14-rc1

2021-09-19 Thread Sudip Mukherjee
Hi Linus, On Sun, Sep 19, 2021 at 12:06 AM Linus Torvalds wrote: > > On Sat, Sep 18, 2021 at 3:48 PM Sudip Mukherjee > wrote: > > > > Also, I have now tested by reverting those two commits and I still get > > the same trace on rpi4. > > Ok. I'm afraid we really need to have the VC4 people

Re: [git pull] drm for 5.14-rc1

2021-09-19 Thread Michael Stapelberg
Sure, no problem. Here are the patch files that make it work for me: https://github.com/gokrazy/kernel/blob/d04d64114aae51aa27752adca6080ed4c9a0c70c/0001-Revert-drm-vc4-hdmi-Make-sure-the-controller-is-powe.patch

Re: [git pull] drm for 5.14-rc1

2021-09-18 Thread Linus Torvalds
On Sat, Sep 18, 2021 at 3:48 PM Sudip Mukherjee wrote: > > Also, I have now tested by reverting those two commits and I still get > the same trace on rpi4. Ok. I'm afraid we really need to have the VC4 people figure it out - I count do the two reverts that are reported to fix the RPi3 issue, but

Re: [git pull] drm for 5.14-rc1

2021-09-18 Thread Sudip Mukherjee
On Sat, Sep 18, 2021 at 11:15 PM Linus Torvalds wrote: > > On Sat, Sep 18, 2021 at 3:00 PM Sudip Mukherjee > wrote: > > > > Its still there. I am seeing it every night. This was from last night > > - https://lava.qa.codethink.co.uk/scheduler/job/164#L1356 > > Note that that web server is not

Re: [git pull] drm for 5.14-rc1

2021-09-18 Thread Linus Torvalds
On Sat, Sep 18, 2021 at 3:00 PM Sudip Mukherjee wrote: > > Its still there. I am seeing it every night. This was from last night > - https://lava.qa.codethink.co.uk/scheduler/job/164#L1356 Note that that web server is not available at least to me. Looks like some internal name or limited dns, I

Re: [git pull] drm for 5.14-rc1

2021-09-18 Thread Linus Torvalds
On Sat, Sep 18, 2021 at 1:13 PM Michael Stapelberg wrote: > > > Michael - do things work if you revert those two (sadly, they don't > > revert cleanly exactly _because_ of the other changes in the same > > area)? > > Reverting only 9984d6664ce9 is not sufficient, but reverting both > 9984d6664ce9

Re: [git pull] drm for 5.14-rc1

2021-09-18 Thread Sudip Mukherjee
Hi Linus, On Sat, Sep 18, 2021 at 8:24 PM Linus Torvalds wrote: > > On Sat, Sep 18, 2021 at 2:18 AM Michael Stapelberg > wrote: > > > > torvalds at linux-foundation.org (Linus Torvalds) writes: > > > Did I fix it up correctly? Who knows. The code makes more sense to me > > > now and seems

Re: [git pull] drm for 5.14-rc1

2021-09-18 Thread Michael Stapelberg
On Sat, 18 Sept 2021 at 21:24, Linus Torvalds wrote: > > On Sat, Sep 18, 2021 at 2:18 AM Michael Stapelberg > wrote: > > > > torvalds at linux-foundation.org (Linus Torvalds) writes: > > > Did I fix it up correctly? Who knows. The code makes more sense to me > > > now and seems valid. But I

Re: [git pull] drm for 5.14-rc1

2021-09-18 Thread Linus Torvalds
On Sat, Sep 18, 2021 at 2:18 AM Michael Stapelberg wrote: > > torvalds at linux-foundation.org (Linus Torvalds) writes: > > Did I fix it up correctly? Who knows. The code makes more sense to me > > now and seems valid. But I really *really* want to stress how locking > > is important. > > As far

Re: [git pull] drm for 5.14-rc1

2021-09-18 Thread Simon Ser
CC Emma and Maxime On Saturday, September 18th, 2021 at 11:18, Michael Stapelberg wrote: > Hi, > > torvalds at linux-foundation.org (Linus Torvalds) writes: > > Did I fix it up correctly? Who knows. The code makes more sense to me > > now and seems valid. But I really *really* want to stress

Re: [git pull] drm for 5.14-rc1

2021-09-18 Thread Michael Stapelberg
Hi, torvalds at linux-foundation.org (Linus Torvalds) writes: > Did I fix it up correctly? Who knows. The code makes more sense to me > now and seems valid. But I really *really* want to stress how locking > is important. As far as I can tell, this merge conflict resolution made my Raspberry Pi

Re: [git pull] drm for 5.14-rc1

2021-07-01 Thread Felix Kuehling
Am 2021-07-01 um 4:15 p.m. schrieb Linus Torvalds: > On Wed, Jun 30, 2021 at 9:34 PM Dave Airlie wrote: >> Hi Linus, >> >> This is the main drm pull request for 5.14-rc1. >> >> I've done a test pull into your current tree, and hit two conflicts >> (one in vc4, one in amdgpu), both seem pretty

Re: [git pull] drm for 5.14-rc1

2021-07-01 Thread pr-tracker-bot
The pull request you sent on Thu, 1 Jul 2021 14:34:15 +1000: > git://anongit.freedesktop.org/drm/drm tags/drm-next-2021-07-01 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/e058a84bfddc42ba356a2316f2cf1141974625c9 Thank you! -- Deet-doot-dot, I am a bot.

Re: [git pull] drm for 5.14-rc1

2021-07-01 Thread Linus Torvalds
On Wed, Jun 30, 2021 at 9:34 PM Dave Airlie wrote: > > Hi Linus, > > This is the main drm pull request for 5.14-rc1. > > I've done a test pull into your current tree, and hit two conflicts > (one in vc4, one in amdgpu), both seem pretty trivial, the amdgpu one > is recent and sfr sent out a