dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
To: xen-devel@lists.xenproject.org, dri-devel@lists.freedesktop.org
Cc: sstabellini@kernel.org, stable@vger.kernel.org, dan.carpenter@oracle.com
Subject: Re: [PATCH v2 2/5] drm/xen-front: Fix misused IS_ERR_OR_NULL checks
Date: Wed, 19 Aug 2020 23:56:34 +0000	[thread overview]
Message-ID: <20200819235634.BB9D621744@mail.kernel.org> (raw)
In-Reply-To: <20200813062113.11030-3-andr2000@gmail.com>

Hi

[This is an automated email]

This commit has been processed because it contains a "Fixes:" tag
fixing commit: c575b7eeb89f ("drm/xen-front: Add support for Xen PV display frontend").

The bot has tested the following trees: v5.8.1, v5.7.15, v5.4.58, v4.19.139.

v5.8.1: Build OK!
v5.7.15: Build OK!
v5.4.58: Failed to apply! Possible dependencies:
    4c1cb04e0e7a ("drm/xen: fix passing zero to 'PTR_ERR' warning")
    93adc0c2cb72 ("drm/xen: Simplify fb_create")

v4.19.139: Failed to apply! Possible dependencies:
    4c1cb04e0e7a ("drm/xen: fix passing zero to 'PTR_ERR' warning")
    93adc0c2cb72 ("drm/xen: Simplify fb_create")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks
Sasha
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-08-19 23:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13  6:21 [PATCH v2 0/5] Fixes and improvements for Xen pvdrm Oleksandr Andrushchenko
2020-08-13  6:21 ` [PATCH v2 1/5] xen/gntdev: Fix dmabuf import with non-zero sgt offset Oleksandr Andrushchenko
2020-08-13  6:21 ` [PATCH v2 2/5] drm/xen-front: Fix misused IS_ERR_OR_NULL checks Oleksandr Andrushchenko
2020-08-19 23:56   ` Sasha Levin [this message]
2020-08-20  7:14     ` Oleksandr Andrushchenko
2020-08-13  6:21 ` [PATCH v2 3/5] drm/xen-front: Add YUYV to supported formats Oleksandr Andrushchenko
2020-08-13  6:21 ` [PATCH v2 4/5] xen: Sync up with the canonical protocol definition in Xen Oleksandr Andrushchenko
2020-08-13  6:21 ` [PATCH v2 5/5] drm/xen-front: Pass dumb buffer data offset to the backend Oleksandr Andrushchenko
2020-08-13  6:32 ` [PATCH v2 0/5] Fixes and improvements for Xen pvdrm Oleksandr Andrushchenko
2020-08-13  7:05   ` Jürgen Groß
2020-08-13  7:21     ` Oleksandr Andrushchenko
2020-08-13 15:02 ` Jürgen Groß
2020-08-13 15:10   ` Oleksandr Andrushchenko
2020-08-13 15:13     ` Jürgen Groß
2020-08-13 16:30       ` Oleksandr Andrushchenko

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=20200819235634.BB9D621744@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=dan.carpenter@oracle.com \
    --cc=sstabellini@kernel.org \
    --cc=stable@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox