From: ssantosh@kernel.org (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/3] soc: few non crtical fixes for 3.19
Date: Wed, 12 Nov 2014 17:59:40 -0800 [thread overview]
Message-ID: <1415843982-5739-1-git-send-email-ssantosh@kernel.org> (raw)
The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:
Linux 3.18-rc1 (2014-10-19 18:08:38 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git tags/keystone-driver-soc
for you to fetch changes up to 148bb0439adeeae466dca31dd4c643e194bee023:
soc: ti: knav_qmss_queue: Use list_for_each_entry_safe to prevent use after free (2014-11-03 10:22:06 -0800)
----------------------------------------------------------------
Keystone SOC Navigator driver non critical fixes frm Alex for 3.19
- Use list_for_each_entry_safe to prevent use after free
- Return proper error if devm_kzalloc fails
- Use list_first_entry_or_null() at appropriate places
----------------------------------------------------------------
Axel Lin (4):
soc: ti: Use list_first_entry_or_null() at appropriate places
soc: ti: knav_qmss_queue: Fix unbalanced locking ins knav_pool_create()
soc: ti: knav_qmss_queue: Return proper error if devm_kzalloc fails
soc: ti: knav_qmss_queue: Use list_for_each_entry_safe to prevent use after free
drivers/soc/ti/knav_qmss.h | 8 ++++----
drivers/soc/ti/knav_qmss_queue.c | 13 +++++++------
2 files changed, 11 insertions(+), 10 deletions(-)
next reply other threads:[~2014-11-13 1:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 1:59 Santosh Shilimkar [this message]
2014-11-13 1:59 ` [GIT PULL 2/3] ARM: keystone: config updates for 3.19 Santosh Shilimkar
2014-11-20 12:14 ` Arnd Bergmann
2014-11-21 17:19 ` santosh shilimkar
2014-11-13 1:59 ` [GIT PULL 3/3] ARM: Keystone dts " Santosh Shilimkar
2014-11-20 12:21 ` Arnd Bergmann
2014-11-20 12:19 ` [GIT PULL 1/3] soc: few non crtical fixes " Arnd Bergmann
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=1415843982-5739-1-git-send-email-ssantosh@kernel.org \
--to=ssantosh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).