All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Johan Hovold <johan@kernel.org>
Cc: Tore Anderson <tore@fud.no>, stable@vger.kernel.org
Subject: Re: [PATCH] USB: serial: option: add HP lt4132
Date: Mon, 10 Dec 2018 19:03:25 -0500	[thread overview]
Message-ID: <20181211000325.GL97256@sasha-vm> (raw)
In-Reply-To: <20181210085317.GB31358@localhost>

On Mon, Dec 10, 2018 at 09:53:17AM +0100, Johan Hovold wrote:
>On Sun, Dec 09, 2018 at 03:21:00PM +0000, 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: v4.19.8, v4.14.87, v4.9.144, v4.4.166, v3.18.128,
>>
>> v4.19.8: Build OK!
>> v4.14.87: Build OK!
>> v4.9.144: Build OK!
>> v4.4.166: Build OK!
>> v3.18.128: Failed to apply! Possible dependencies:
>>     5d03a2fd2292 ("USB: serial: option: add device ID for HP lt2523 (Novatel E371)")
>
>I thought 3.18 was finally EOLed?

Sadly it's still alive.

>> How should we proceed with this patch?
>
>It applies just fine to mainline, but looks like your scripts found a
>missing stable patch which would also make it apply to 3.18 without the
>need to adjust any context.

I'll grab 5d03a2fd2292 too, as it's also adding IDs.

--
Thanks,
Sasha

  reply	other threads:[~2018-12-11  0:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-08 18:05 USB: serial: option: add HP lt4132 Tore Anderson
2018-12-08 18:05 ` [PATCH] " Tore Anderson
2018-12-09 15:21 ` Sasha Levin
2018-12-10  8:53   ` Johan Hovold
2018-12-11  0:03     ` Sasha Levin [this message]
2018-12-11 11:20       ` Johan Hovold
  -- strict thread matches above, loose matches on Subject: below --
2018-12-10  9:06 Johan Hovold
2018-12-10  9:06 ` [PATCH] " Johan Hovold

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=20181211000325.GL97256@sasha-vm \
    --to=sashal@kernel.org \
    --cc=johan@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tore@fud.no \
    /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.