netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wei Yang <weiyang@linux.vnet.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: weiyang@linux.vnet.ibm.com, netdev@vger.kernel.org
Subject: Re: [PATCH] net/mlx4_core: Preserve pci_dev_data after __mlx4_remove_one()
Date: Wed, 28 May 2014 10:46:50 +0800	[thread overview]
Message-ID: <20140528024650.GA8602@richard> (raw)
In-Reply-To: <20140527.193737.22275611325169063.davem@davemloft.net>

On Tue, May 27, 2014 at 07:37:37PM -0700, David Miller wrote:
>From: Wei Yang <weiyang@linux.vnet.ibm.com>
>Date: Wed, 28 May 2014 09:48:48 +0800
>
>> I haven't done some backporting job before, so not sure how to and which
>> attention I should pay.
>> 
>> I guess I should use this tree:
>>      git://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux-stable.git
>> and apply it on tag v3.14.4?
>
>That is Jiri's personal tree strictly for 3.12 -stable development.
>
>The real -stable tree is at:
>
>	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>
>And you should make versions for the most recent tags for 3.14, 3.10, 3.4,
>and 3.2

Ok, this may take some time to verify.

Could I backport it one version by one version? Or need to send out for these
four versions at the same time?

-- 
Richard Yang
Help you, Help me

  reply	other threads:[~2014-05-28  2:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27 18:54 [PATCH] net/mlx4_core: Preserve pci_dev_data after __mlx4_remove_one() David Miller
2014-05-28  1:48 ` Wei Yang
2014-05-28  2:37   ` David Miller
2014-05-28  2:46     ` Wei Yang [this message]
2014-05-28  3:18       ` David Miller
2014-05-28  3:26         ` Wei Yang
2014-05-31  2:46         ` Wei Yang
2014-05-31  6:35           ` David Miller
2014-06-01  2:41             ` 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=20140528024650.GA8602@richard \
    --to=weiyang@linux.vnet.ibm.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.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 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).