All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: backports@vger.kernel.org
Subject: Re: [PATCH 0/4] backports: make compatible with kernel 4.14-rc
Date: Thu, 21 Sep 2017 15:23:30 +0200	[thread overview]
Message-ID: <1506000210.2048.2.camel@sipsolutions.net> (raw)
In-Reply-To: <20170917165813.17580-1-hauke@hauke-m.de> (sfid-20170917_185834_631711_EC2A368E)

On Sun, 2017-09-17 at 18:58 +0200, Hauke Mehrtens wrote:
> This makes it possible to base backports on top of Linux 4.14-rc1.

All applied, thanks.

> I got these compile results:
> 
> 1   3.0.101             [  FAIL  ]
> 2   3.1.10              [  FAIL  ]
> 3   3.2.92              [  FAIL  ]
> 4   3.3.8               [  FAIL  ]
> 5   3.4.110             [  LINK  ]
> 6   3.5.7               [  LINK  ]
> 7   3.6.11              [  LINK  ]
> 8   3.7.10              [  LINK  ]
> 9   3.8.13              [  LINK  ]
> 10  3.9.11              [  LINK  ]
> 11  3.10.107            [  FAIL  ]
> 12  3.11.10             [  FAIL  ]
> 13  3.12.74             [  FAIL  ]

All of those really seem to have mostly tracing issues :(

johannes

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

      parent reply	other threads:[~2017-09-21 13:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-17 16:58 [PATCH 0/4] backports: make compatible with kernel 4.14-rc Hauke Mehrtens
2017-09-17 16:58 ` [PATCH 1/4] patches: refresh patches on v4.14-rc1 Hauke Mehrtens
2017-09-17 16:58 ` [PATCH 2/4] header: add uuid backports Hauke Mehrtens
2017-09-17 16:58 ` [PATCH 3/4] header: add UUID_STRING_LEN Hauke Mehrtens
2017-09-17 16:58 ` [PATCH 4/4] header: add ether_addr_to_u64() and u64_to_ether_addr() Hauke Mehrtens
2017-09-21 13:23 ` 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=1506000210.2048.2.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=backports@vger.kernel.org \
    --cc=hauke@hauke-m.de \
    /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.