All of lore.kernel.org
 help / color / mirror / Atom feed
From: <jackie.huang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] ppp: fix building with linux-4.8
Date: Fri, 14 Oct 2016 08:50:09 +0800	[thread overview]
Message-ID: <cover.1476345470.git.jackie.huang@windriver.com> (raw)

From: Jackie Huang <jackie.huang@windriver.com>

--
The following changes since commit 371ab635086e2878ada1f00a59c7ec826481ba0a:

  build-appliance-image: Update to master head revision (2016-10-11 23:43:28 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib.git jhuang0/d_ppp-linux-4.8_161008-0
  http://git.pokylinux.org/cgit.cgi//log/?h=jhuang0/d_ppp-linux-4.8_161008-0

Jackie Huang (2):
  Revert "linux-libc-headers: fix in/if.h includes"
  ppp: fix building with linux-4.8

 .../ppp/ppp/ppp-fix-building-with-linux-4.8.patch  | 44 ++++++++++++
 meta/recipes-connectivity/ppp/ppp_2.4.7.bb         |  1 +
 .../0001-ppp-fix-in-if.h-includes.patch            | 83 ----------------------
 .../linux-libc-headers/linux-libc-headers_4.8.bb   |  4 --
 4 files changed, 45 insertions(+), 87 deletions(-)
 create mode 100644 meta/recipes-connectivity/ppp/ppp/ppp-fix-building-with-linux-4.8.patch
 delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-ppp-fix-in-if.h-includes.patch

-- 
2.8.3



             reply	other threads:[~2016-10-14  1:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14  0:50 jackie.huang [this message]
2016-10-14  0:50 ` [PATCH 1/2] Revert "linux-libc-headers: fix in/if.h includes" jackie.huang
2016-10-14  0:50 ` [PATCH 2/2] ppp: fix building with linux-4.8 jackie.huang
2016-10-21 14:01   ` Andreas Oberritter
2016-10-24  1:11     ` Huang, Jie (Jackie)
2016-10-24  7:22       ` Andreas Oberritter

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=cover.1476345470.git.jackie.huang@windriver.com \
    --to=jackie.huang@windriver.com \
    --cc=openembedded-core@lists.openembedded.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 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.