summaryrefslogtreecommitdiffstats
path: root/Kbuild
diff options
context:
space:
mode:
authorJan Beulich <JBeulich@suse.com>2012-03-05 18:11:31 +0100
committerKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>2012-03-13 19:15:29 +0100
commitbd0d5aa417d40d6b996fb7b5c926bcecd56c8984 (patch)
tree7e05120b899c9bcabe1422d0c582c49d97cd1037 /Kbuild
parentxen/enlighten: Expose MWAIT and MWAIT_LEAF if hypervisor OKs it. (diff)
downloadlinux-bd0d5aa417d40d6b996fb7b5c926bcecd56c8984.tar.xz
linux-bd0d5aa417d40d6b996fb7b5c926bcecd56c8984.zip
xenbus: don't free other end details too early
The individual drivers' remove functions could legitimately attempt to access this information (for logging messages if nothing else). Note that I did not in fact observe a problem anywhere, but I came across this while looking into the reasons for what turned out to need the fix at https://lkml.org/lkml/2012/3/5/336 to vsprintf(). Signed-off-by: Jan Beulich <jbeulich@suse.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions