Hello Vasu, Every now and then I receive an e-mail from an FCoE user who runs an older kernel reporting an issue that was fixed by the patches that were accepted upstream in kernel 3.13 (see also http://thread.gmane.org/gmane.linux.scsi.open-fcoe.devel/12132). This made me wonder what the policy is for sending patches to the stable tree ? The list of patches I would like to see being sent to the stable tree is as follows (tested on top of kernel v3.10.62):
648a179a5a28f2f16efc4711fb5a4c38d1ef1ceb libfc: Reject PLOGI from nodes with incompatible role 129a350a92fa6ea19c6ff3a60d0424ea76989060 fcoe: Fix smatch warning in fcoe_fdmi_info function 86a78a3157c292fc73dc2bcb11609f8ed973437a fcoe: fix the link error status block sparse warnings 38446b470d49567aa1b55045e65dc3bb9be40b2a libfc: Differentiate echange timer cancellation debug statements 14122e6901ea4b89a7a58b75e6bc2e9db17c768d libfcoe: Fix meaningless log statement 5a95e4d9b51622a99d881b9f415413158782a034 fcoe: Stop fc_rport_priv structure leak ca1e26dace27b08aab4406c7542f12956b996c6c fcoe: Reduce number of sparse warnings a6f50989c73f51fd0208b0f7fb38c8ef369b940e fcoe: ensure that skb placed on the fip_recv_list are unshared fe594938f703884e8531a985bdf8f055ff6f797c fcoe: make sure fcoe frames are unshared prior to manipulating them 29bce4de2b36291e52a027e7b656a8332674ef4e fcoe: cleanup return codes from fcoe_rcv f596d9a0cca64bcc635b21c76f7ea426b7dc48d2 libfc: Source code comment spelling fixes 93b31c44dee5f6a3d193e0a91fd1842a16fe8e9e libfc: Debug code fixes 9005094109bd4cce7e8ad90f619f4726b03a59b9 libfc: Micro-optimize fc_setup_exch_mgr() 2d56fbdfd947a81905e4f2551d95705a85aad08b libfc: Clarify fc_exch_find() e3f112a7cc51427ee9938026168c95a3cedab037 libfc: Fix a race in fc_exch_timer_set_locked() d174e95ed5ff812bd11b8b2d098e81b2ba266e22 libfc: Protect ep->esb_stat changes via ex_lock 8b1567d9603c87857eab1869a57e66ee4915716d libfc: Avoid that sending after an abort triggers a kernel warning c946a1c2d92ea54cddebc1ac2204e214dc63692e libfc: Reduce exchange lock contention in fc_exch_recv_abts() b52181d2bf17ab7eb2a0fb1f76e45d7adbad645d libfc: Do not invoke the response handler after fc_exch_done() 78bf612e8f2af71d4f7453d9cf35eaa67403c825 fcp: Do not interpret check condition as underrun 6c40010e03547930fc5465087a72080cdabf6d24 fcoe: Declare fcoe_ctlr_mode_set() static d72ad2b74816b9920659093ed609a6c391287f5c fcoe: Add missing newlines in debug messages 180db363920cdbf5d7462b1d6fb6a999071a0d4d fcoe: Reduce fcoe_sysfs_fcf_add() stack usage f298717281fc505949fcf6bdf5ba051fa65759b3 libfcoe: Make fcoe_sysfs optional / fix fnic NULL exception a08cdd23d184bd01f26ba3e3cff056bed60aa90a fcoe: Fix missing mutex_unlock in fcoe_sysfs_fcf_add error path Thanks, Bart. _______________________________________________ fcoe-devel mailing list fcoe-devel@open-fcoe.org http://lists.open-fcoe.org/mailman/listinfo/fcoe-devel