Hi Greg,

(Apologies to those that got duplicates of this.  I forgot to CC the
stable list on my first sending of this.  Mea culpa.)

I went through the current Fedora F17 kernel and found quite a few
patches we are carrying for bugs that should probably go to stable.
Some of them have the stable tag in the upstream commit but don't seem
to be queued up in the stable-queue tree on kernel.org.  Maybe you
already have those stashed somewhere.

At any rate, I've listed the commits below along with the Fedora bugs
they fix.  I've CC'd Dave and John as a few of them are net/wireless
related and I know Dave handles those patches differently.

rhbz 830359
9bd0c15fc drm/nouveau/fbcon: using nv_two_heads is not a good idea

rhbz 828824
b7abee6ef tg3: Apply short DMA frag workaround to 5906

rhbz 834910
b03738430 ACPI video: Still use ACPI backlight control if _DOS doesn't
exist

rhbz 832927
6bb51c70c ath9k: fix panic caused by returning a descriptor we have
queued for reuse

rhbz 832867
4fe7efdbd mm: correctly synchronize rss-counters at exit/exec

rhbz 835019
080399aaa block: don't mark buffers beyond end of disk as mapped

rhbz 828731
931cb03af ath9k_htc: configure bssid on ASSOC/IBSS change

rhbz 831807
6a0bdffa0 SCSI & usb-storage: add try_rc_10_first flag

rhbz 829880
00001880c USB: qmi_wwan: Make forced int 4 whitelist generic
f7142e6c2 USB: qmi_wwan: Add ZTE (Vodafone) K3520-Z
b9f90eb27 net: qmi_wwan: fix Gobi device probing

rhbz 822825
26c191788 mm: pmd_read_atomic: fix 32bit PAE pmd walk vs pmd_populate
SMP race condition
e4eed03fd thp: avoid atomic64_read in pmd_read_atomic for 32bit PAE

rhbz 795176
0fde0a8cf rtl8187: ->brightness_set can not sleep

rhbz 814278
b92946e29 macvtap: zerocopy: validate vectors before building skb

rhbz 817298
a141e6a00 net/wireless: ipw2x00: add supported cipher suites to wiphy
initialization

Hopefully that helps.  Let me know if you have questions.

josh
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to