From: Jia-Ju Bai <baijiaju1990@163.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: linux.nics@intel.com,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
bruce.w.allan@intel.com, jesse.brandeburg@intel.com,
davem@davemloft.net
Subject: Re: [PATCH v3 1/3] igb: Add igb_disable_sriov in error handling
Date: Tue, 23 Dec 2014 23:06:12 +0800 [thread overview]
Message-ID: <549984E4.6020406@163.com> (raw)
In-Reply-To: <1419343393.2470.14.camel@jtkirshe-mobl>
On 12/23/2014 10:03 PM, Jeff Kirsher wrote:
>
> No it is not. If you were sending a patch (which has already been
> accepted upstream) to the stable trees, then you would specify what
> stable kernels the patch applies to. In your case, I would not consider
> your patches critical for the stable trees.
>
> So when sending patches, you inform the maintainer (i.e. me) what tree
> you want your patch applied by stating either "net" or "net-next" in the
> title. For example, this patch would be titled:
>
> [net v3 1/3] igb: Add igb_disable_sriov in error handling
>
> Which lets me know you want your patch applied to the "net" tree. If it
> were not a fix, then it would go into the "net-next" tree by using the
> title:
>
> [net-next v3 1/3] igb: Add igb_disable_sriov in error handling
>
>
Thanks!
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
prev parent reply other threads:[~2014-12-23 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 7:17 [PATCH v3 1/3] igb: Add igb_disable_sriov in error handling Jia-Ju Bai
2014-12-23 7:17 ` [PATCH v3 2/3] igb: Add pci_disable_pcie_error_reporting " Jia-Ju Bai
2014-12-23 7:17 ` [PATCH v3 3/3] igb: Fix a memory leak in igb_probe Jia-Ju Bai
2014-12-23 7:29 ` Varka Bhadram
2014-12-23 11:23 ` [PATCH v3 1/3] igb: Add igb_disable_sriov in error handling Sergei Shtylyov
2014-12-23 13:22 ` Jia-Ju Bai
2014-12-23 14:03 ` Jeff Kirsher
2014-12-23 15:06 ` Jia-Ju Bai [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=549984E4.6020406@163.com \
--to=baijiaju1990@163.com \
--cc=bruce.w.allan@intel.com \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=linux.nics@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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).