From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: linux-scsi <linux-scsi@vger.kernel.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Nicholas Bellinger <nab@linux-iscsi.org>
Subject: [GIT PULL] target patches for .39 scsi-misc
Date: Thu, 24 Feb 2011 17:14:48 -0800 [thread overview]
Message-ID: <1298596488-1661-1-git-send-email-nab@linux-iscsi.org> (raw)
From: Nicholas Bellinger <nab@linux-iscsi.org>
Hi James,
Here are the remaining non critical bugfixes and improvements originally
slated for .38, but which have been queued as .39 misc items upon your
request.
These patches have already been posted a number of times to linux-scsi,
so to reduce the extra noise I am sending an PULL request for these
minor changes. This tree is against .38-rc6, and please apply to
scsi-misc for .39 from here:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/scsi-post-merge-2.6.git for-39-misc
Thanks!
Signed-off-by: Nicholas A. Bellinger <nab@linux-iscsi.org>
Christoph Hellwig (1):
target: remove EXTRA_CFLAGS
Dan Carpenter (2):
target: fix dubious one-bit signed bitfield
target: Convert rd_build_device_space() to use errno
Fubo Chen (3):
target: Remove unnecessary hba_dev_list walk + release from
core_delete_hba
target: Minor sparse warning fixes and annotations
target: Fix generated *_drop_nodeacl() handler in tcm_mod_builder.py
Jesper Juhl (2):
target/file: Fix memory leak in fd_set_configfs_dev_params().
target: Avoid mem leak and needless work in transport_generic_get_mem
Nicholas Bellinger (9):
target/iblock: Fix memory leak in iblock_set_configfs_dev_params
target: Fix memory leaks in
target_core_dev_pr_store_attr_res_aptpl_metadata
target: tcm_mod_builder.py generated Makefile cleanups
target: Convert backend ->create_virtdevice() call to return ERR_PTR
target: Remove unnecessary se_clear_dev_ports legacy code
target: Remove spurious double cast from structure macro accessors
target: Convert TMR REQ/RSP definitions to target namespace
target core v4.0.0-rc7
target: Fix bogus return in transport_add_device_to_core_hba failure
path
Roland Dreier (1):
target: Fix memory leak on error path
Documentation/target/tcm_mod_builder.py | 18 +++++-----
drivers/target/Makefile | 1 -
drivers/target/target_core_configfs.c | 37 ++++++++++++++++++++--
drivers/target/target_core_device.c | 40 ++----------------------
drivers/target/target_core_fabric_lib.c | 1 +
drivers/target/target_core_file.c | 26 ++++++++++++---
drivers/target/target_core_hba.c | 15 +--------
drivers/target/target_core_iblock.c | 28 ++++++++++------
drivers/target/target_core_pscsi.c | 22 ++++++++-----
drivers/target/target_core_rd.c | 15 +++++----
drivers/target/target_core_rd.h | 2 -
drivers/target/target_core_transport.c | 37 +++++++++------------
include/target/target_core_base.h | 38 +++++++++++-----------
include/target/target_core_fabric_ops.h | 2 +-
include/target/target_core_tmr.h | 52 +++++++++++++------------------
include/target/target_core_transport.h | 4 ++
16 files changed, 170 insertions(+), 168 deletions(-)
--
1.7.4.1
next reply other threads:[~2011-02-25 1:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 1:14 Nicholas A. Bellinger [this message]
2011-02-25 14:34 ` [GIT PULL] target patches for .39 scsi-misc James Bottomley
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=1298596488-1661-1-git-send-email-nab@linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.kernel.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).