All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	DRI <dri-devel@lists.freedesktop.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: linux-next: build warning after merge of the drm-intel tree
Date: Mon, 22 Jan 2024 19:22:35 +0200	[thread overview]
Message-ID: <87o7ddnuzo.fsf@intel.com> (raw)
In-Reply-To: <20240122092520.68a86f48@canb.auug.org.au>

On Mon, 22 Jan 2024, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> [1] https://patchwork.freedesktop.org/patch/msgid/20231114081033.27343-1-bagasdotme@gmail.com
>
> This is still not fixed.

Thanks for the reminder. Commit 1a84c213146a ("drm/dp_mst: Separate
@failing_port list in drm_dp_mst_atomic_check_mgr() comment") in
drm-misc-fixes, likely to show up in -rc2.

BR,
Jani.


-- 
Jani Nikula, Intel

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	DRI <dri-devel@lists.freedesktop.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the drm-intel tree
Date: Mon, 22 Jan 2024 19:22:35 +0200	[thread overview]
Message-ID: <87o7ddnuzo.fsf@intel.com> (raw)
In-Reply-To: <20240122092520.68a86f48@canb.auug.org.au>

On Mon, 22 Jan 2024, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> [1] https://patchwork.freedesktop.org/patch/msgid/20231114081033.27343-1-bagasdotme@gmail.com
>
> This is still not fixed.

Thanks for the reminder. Commit 1a84c213146a ("drm/dp_mst: Separate
@failing_port list in drm_dp_mst_atomic_check_mgr() comment") in
drm-misc-fixes, likely to show up in -rc2.

BR,
Jani.


-- 
Jani Nikula, Intel

  reply	other threads:[~2024-01-22 17:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14  3:17 [Intel-gfx] linux-next: build warning after merge of the drm-intel tree Stephen Rothwell
2023-11-14  3:17 ` Stephen Rothwell
2023-11-14  3:17 ` Stephen Rothwell
2023-11-14  8:22 ` [Intel-gfx] " Jani Nikula
2023-11-14  8:22   ` Jani Nikula
2023-11-14  8:22   ` Jani Nikula
2023-11-14  8:53   ` [Intel-gfx] " Jani Nikula
2023-11-14  8:53     ` Jani Nikula
2024-01-21 22:25     ` Stephen Rothwell
2024-01-21 22:25       ` Stephen Rothwell
2024-01-22 17:22       ` Jani Nikula [this message]
2024-01-22 17:22         ` Jani Nikula
  -- strict thread matches above, loose matches on Subject: below --
2024-10-01  3:43 Stephen Rothwell
2024-10-11  5:57 ` Stephen Rothwell
2024-06-12  4:11 Stephen Rothwell
2024-07-14 23:12 ` Stephen Rothwell
2024-07-15  4:21   ` Golani, Mitulkumar Ajitkumar
2024-07-15 12:13     ` Maarten Lankhorst
2024-07-30 10:10       ` Stephen Rothwell
2024-04-18  6:38 Stephen Rothwell
2024-02-19  5:17 Stephen Rothwell
2022-11-30  3:45 Stephen Rothwell
2022-11-30  3:45 ` Stephen Rothwell
2015-05-07  5:29 Stephen Rothwell
2015-05-07  5:29 ` Stephen Rothwell

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=87o7ddnuzo.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=sfr@canb.auug.org.au \
    /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.