From: Wei Yang <weiyang@linux.vnet.ibm.com>
To: Wei Yang <weiyang@linux.vnet.ibm.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
Amir Vadai <amirv@mellanox.com>,
Jack Morgenstein <jackm@dev.mellanox.co.il>,
Or Gerlitz <ogerlitz@mellanox.com>
Subject: Re: [PATCH 3.14-stable] net/mlx4_core: Preserve pci_dev_data after __mlx4_remove_one()
Date: Sun, 1 Jun 2014 15:38:53 +0800 [thread overview]
Message-ID: <20140601073853.GA8635@richard> (raw)
In-Reply-To: <1401607475-8367-1-git-send-email-weiyang@linux.vnet.ibm.com>
David,
Following are the backport of this patch to 3.14, 3.10, 3.4 and 3.2 stable
tree.
On 3.14, only this patch is backported.
On 3.10, a previous related one "pass pci_device_id.driver_data to
__mlx4_init_one during reset" is backported too.
On 3.4, "pass pci_device_id.driver_data to __mlx4_init_one during reset" is
not backported, since the slot_reset handler is not presented.
While another one, "Stash PCI ID driver_data in mlx4_priv structure"
is backported to make this patch valid on this version.
On 3.2, The same as 3.4.
All version are compiled successfully. 3.14 and 3.10 are verified, while 3.4
and 3.2 are not.
I am not sure how to make them all in one big patch set, so send them
seperatedly. Each version is contained in one patch set. If there is a better
way for you to merge them, please let me know.
At last, Happy Children's Day for all :-)
--
Richard Yang
Help you, Help me
next prev parent reply other threads:[~2014-06-01 7:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 7:24 [PATCH 3.14-stable] net/mlx4_core: Preserve pci_dev_data after __mlx4_remove_one() Wei Yang
2014-06-01 7:38 ` Wei Yang [this message]
2014-06-01 9:30 ` Or Gerlitz
2014-06-01 9:36 ` Or Gerlitz
2014-06-01 10:52 ` Or Gerlitz
2014-06-02 13:53 ` Wei Yang
2014-06-03 8:43 ` Or Gerlitz
2014-06-04 1:44 ` Wei Yang
2014-06-17 2:49 ` Wei Yang
2014-06-17 3:03 ` David Miller
2014-06-17 3:08 ` Wei Yang
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=20140601073853.GA8635@richard \
--to=weiyang@linux.vnet.ibm.com \
--cc=amirv@mellanox.com \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=jackm@dev.mellanox.co.il \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.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 NNTP newsgroup(s).