All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Siniša Bandin" <sinisa@4net.rs>, "Souza, Jose" <jose.souza@intel.com>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] Linux 5.6-rc2
Date: Mon, 02 Mar 2020 19:04:31 +0200	[thread overview]
Message-ID: <87sgiqpu1s.fsf@intel.com> (raw)
In-Reply-To: <a1c918b663805e8213a1229edb87883c@4net.rs>

On Mon, 02 Mar 2020, Siniša Bandin <sinisa@4net.rs> wrote:
> Sorry to bother, but still a "no go" in rc4 (at the same time, 5.5.7 
> works OK).
>
> Is there anything else I could do to help fix this?

Please wait for the patch to be actually merged to Linus' tree. I assume
it'll make it to v5.6-rc5.

Thanks,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Siniša Bandin" <sinisa@4net.rs>, "Souza, Jose" <jose.souza@intel.com>
Cc: airlied@gmail.com, intel-gfx@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] Linux 5.6-rc2
Date: Mon, 02 Mar 2020 19:04:31 +0200	[thread overview]
Message-ID: <87sgiqpu1s.fsf@intel.com> (raw)
In-Reply-To: <a1c918b663805e8213a1229edb87883c@4net.rs>

On Mon, 02 Mar 2020, Siniša Bandin <sinisa@4net.rs> wrote:
> Sorry to bother, but still a "no go" in rc4 (at the same time, 5.5.7 
> works OK).
>
> Is there anything else I could do to help fix this?

Please wait for the patch to be actually merged to Linus' tree. I assume
it'll make it to v5.6-rc5.

Thanks,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2020-03-02 17:04 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-16 21:32 Linux 5.6-rc2 Linus Torvalds
2020-02-17  2:08 ` Dave Jones
2020-02-17  2:24   ` Linus Torvalds
2020-02-17  3:02     ` Josef Bacik
2020-02-17  5:08       ` Linus Torvalds
2020-02-17 12:30         ` David Sterba
2020-02-17 16:45           ` Dave Jones
2020-02-17 16:04         ` Filipe Manana
2020-02-17 16:21 ` Chris Wilson
2020-02-17 21:20   ` Linus Torvalds
2020-02-17 21:29     ` Chris Wilson
2020-02-20 22:41       ` Rafael J. Wysocki
2020-02-21  0:46         ` Rafael J. Wysocki
2020-02-21  9:19           ` Chris Wilson
     [not found]             ` <CAJZ5v0h07em8y5bXcnUTBcjie8pCttADK9QX9W_cB0WQRcDfGQ@mail.gmail.com>
2020-02-21 18:02               ` Linus Torvalds
2020-02-23 23:57                 ` Rafael J. Wysocki
2020-02-17 18:42 ` sinisa
2020-02-17 20:17   ` Dominik Brodowski
2020-02-21  1:38   ` [Intel-gfx] " Dave Airlie
2020-02-21  1:38     ` Dave Airlie
2020-02-21  2:23     ` [Intel-gfx] " Souza, Jose
2020-02-21  2:23       ` Souza, Jose
2020-02-24 18:24       ` Siniša Bandin
2020-02-24 18:24         ` Siniša Bandin
2020-03-02 16:39       ` Siniša Bandin
2020-03-02 16:39         ` Siniša Bandin
2020-03-02 17:04         ` Jani Nikula [this message]
2020-03-02 17:04           ` Jani Nikula
2020-03-03  7:08           ` Sinisa
2020-03-03  7:08             ` Sinisa

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=87sgiqpu1s.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jose.souza@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sinisa@4net.rs \
    /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.