mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Sasha Levin <sashal@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] virt: vbox: Sanity-check parameter types for hgcm-calls coming from userspace
Date: Sat, 6 Apr 2019 11:33:48 +0200	[thread overview]
Message-ID: <4667d465-15aa-178d-dcbe-9b70d093d55c@redhat.com> (raw)
In-Reply-To: <20190405141526.6035D21872@mail.kernel.org>

Hi,

On 05-04-19 16:15, Sasha Levin wrote:
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
> 
> The bot has tested the following trees: v5.0.6, v4.19.33, v4.14.110, v4.9.167, v4.4.178, v3.18.138.
> 
> v5.0.6: Build OK!
> v4.19.33: Build OK!
> v4.14.110: Failed to apply! Possible dependencies:
>      0ba002bc4393 ("virt: Add vboxguest driver for Virtual Box Guest integration")
> 
> v4.9.167: Failed to apply! Possible dependencies:
>      0ba002bc4393 ("virt: Add vboxguest driver for Virtual Box Guest integration")
> 
> v4.4.178: Failed to apply! Possible dependencies:
>      0ba002bc4393 ("virt: Add vboxguest driver for Virtual Box Guest integration")
> 
> v3.18.138: Failed to apply! Possible dependencies:
>      0ba002bc4393 ("virt: Add vboxguest driver for Virtual Box Guest integration")
> 
> 
> How should we proceed with this patch?

4.14 and older do not have the vboxguest driver, so just applying this to 4.19+ is
fine.

Regards,

Hans

      parent reply	other threads:[~2019-04-06  9:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 12:39 Hans de Goede
     [not found] ` <20190405141526.6035D21872@mail.kernel.org>
2019-04-06  9:33   ` Hans de Goede [this message]

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=4667d465-15aa-178d-dcbe-9b70d093d55c@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@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
all inboxes | Powered by JetHome®