Backports Archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
	Steve deRosier <derosier@gmail.com>
Cc: masashi.honma@gmail.com, backports@vger.kernel.org
Subject: Re: Failed to backport from from Linux 4.4 drivers to Linux 3.10.108
Date: Wed, 09 May 2018 21:27:10 +0200	[thread overview]
Message-ID: <1525894030.6910.12.camel@sipsolutions.net> (raw)
In-Reply-To: <5AF342A2.1030801@broadcom.com> (sfid-20180509_204909_089738_9E2BF01F)

On Wed, 2018-05-09 at 20:49 +0200, Arend van Spriel wrote:
> 
> Do we have docs :-p Anyway, the gentree script checks the spatch version 
> and seems Johannes already took care of the script as well [1]

Yeah I didn't apply it to any other branches though.

johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in

      reply	other threads:[~2018-05-09 19:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08  3:05 Failed to backport from from Linux 4.4 drivers to Linux 3.10.108 Masashi Honma
2018-05-08  9:09 ` Johannes Berg
2018-05-08  8:53   ` Masashi Honma
2018-05-08  9:08     ` Johannes Berg
2018-05-08 21:42       ` Masashi Honma
2018-05-09  7:21         ` Masashi Honma
2018-05-09  7:24           ` Johannes Berg
2018-05-09  7:54             ` Johannes Berg
2018-05-09  8:07               ` Masashi Honma
2018-05-09  8:12                 ` Johannes Berg
2018-05-09  8:51                   ` Masashi Honma
2018-05-09  9:03                     ` Johannes Berg
2018-05-09  9:16                       ` Masashi Honma
2018-05-09  9:24                       ` Masashi Honma
2018-05-09  9:25                         ` Johannes Berg
2018-05-09 14:19                           ` Steve deRosier
2018-05-09 18:49                             ` Arend van Spriel
2018-05-09 19:27                               ` Johannes Berg [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=1525894030.6910.12.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arend.vanspriel@broadcom.com \
    --cc=backports@vger.kernel.org \
    --cc=derosier@gmail.com \
    --cc=masashi.honma@gmail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).