From: Bart Van Assche <bvanassche@acm.org>
To: Greg Kroah-Hartman <greg@kroah.com>
Cc: Ming Lei <ming.lei@canonical.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [0/3] Driver core patches for kernel 3.14
Date: Sat, 04 Jan 2014 14:19:12 +0100 [thread overview]
Message-ID: <52C80A50.3000602@acm.org> (raw)
This series consists of the following three patches:
0001-kobject-Fix-source-code-comment-spelling.patch
0002-firmware-loader-Add-sparse-annotation.patch
0003-driver-core-Fix-use-after-free-triggered-by-bus_unre.patch
next reply other threads:[~2014-01-04 13:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 13:19 Bart Van Assche [this message]
2014-01-04 13:20 ` [PATCH 1/3] kobject: Fix source code comment spelling Bart Van Assche
2014-01-04 13:20 ` [PATCH 2/3] firmware loader: Add sparse annotation Bart Van Assche
2014-01-08 1:40 ` Ming Lei
2014-01-04 13:21 ` [PATCH 3/3] driver-core: Fix use-after-free triggered by bus_unregister() Bart Van Assche
2014-01-08 2:01 ` Ming Lei
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=52C80A50.3000602@acm.org \
--to=bvanassche@acm.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.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).