public inbox for backports@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: backports@vger.kernel.org
Cc: julia.lawall@lip6.fr, oblinger@gmail.com,
	"Luis R. Rodriguez" <mcgrof@suse.com>
Subject: [PATCH 0/5] backports: move up to next-20141117
Date: Thu, 20 Nov 2014 13:16:18 -0800	[thread overview]
Message-ID: <1416518183-7347-1-git-send-email-mcgrof@do-not-panic.com> (raw)

From: "Luis R. Rodriguez" <mcgrof@suse.com>

Here's a few required backport changes to get us up from
next-20141114 to next-20141117. The first two patches are
example *simple* upstream changes we should consider
evaluating the possibility to automatically infer what is
required to do and automatically backport. We'd need to
deduce file renames or file splitting. Consider this as
part of the automation TODO list. It doesn't seem like
we need any special tools for this, but simply some
inference based evaluation of deltas.

Luis R. Rodriguez (5):
  backports: rename wpan-phy.h to cfg802154.h
  backports: address splitting of v4l2-mediabus.h to two files
  backports: bump I2C_SI4713 to v3.13
  backports: backport netdev_rss_key_fill()
  backports: refresh patches for next-20141117

 backport/backport-include/linux/netdevice.h        | 25 ++++++++++++++++++++++
 backport/compat/backport-3.19.c                    | 15 ++++++++++++-
 copy-list                                          |  3 ++-
 dependencies                                       | 17 +++++++++++++++
 .../0032-sriov_configure/igb_sriov_configure.patch |  8 +++----
 .../0033-ndo_vlan_rx_vid/igb_ndo_vlan_rx_vid.patch |  8 +++----
 .../igb_ndo_set_vf_spoofchk.patch                  |  6 +++---
 .../network/0035-skb_no_fcs/igb_skb_no_fcs.patch   |  2 +-
 .../network/0043-ndo_set_vf_rate/igb.patch         |  8 +++----
 .../network/0048-no_ndo_xmit_flush/igb.patch       |  2 +-
 .../network/0049-no-pfmemalloc/igb.patch           |  4 ++--
 11 files changed, 77 insertions(+), 21 deletions(-)

-- 
2.1.1


             reply	other threads:[~2014-11-20 21:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 21:16 Luis R. Rodriguez [this message]
2014-11-20 21:16 ` [PATCH 1/5] backports: rename wpan-phy.h to cfg802154.h Luis R. Rodriguez
2014-11-20 21:22   ` Hauke Mehrtens
2014-11-20 21:31     ` Luis R. Rodriguez
2014-11-20 21:16 ` [PATCH 2/5] backports: address splitting of v4l2-mediabus.h to two files Luis R. Rodriguez
2014-11-20 21:16 ` [PATCH 3/5] backports: bump I2C_SI4713 to v3.13 Luis R. Rodriguez
2014-11-20 21:16 ` [PATCH 4/5] backports: backport netdev_rss_key_fill() Luis R. Rodriguez
2014-11-20 21:16 ` [PATCH 5/5] backports: refresh patches for next-20141117 Luis R. Rodriguez

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=1416518183-7347-1-git-send-email-mcgrof@do-not-panic.com \
    --to=mcgrof@do-not-panic.com \
    --cc=backports@vger.kernel.org \
    --cc=julia.lawall@lip6.fr \
    --cc=mcgrof@suse.com \
    --cc=oblinger@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