From: Andy Grover <agrover@redhat.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: Christoph Hellwig <hch@lst.de>,
target-devel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCHv3 0/8] target: Save memory on unused se_dev_entrys and se_luns
Date: Tue, 23 Sep 2014 10:02:23 -0700 [thread overview]
Message-ID: <5421A79F.9010003@redhat.com> (raw)
In-Reply-To: <1411082258.28382.17.camel@haakon3.risingtidesystems.com>
On 09/18/2014 04:17 PM, Nicholas A. Bellinger wrote:
> I'm currently reviewing #2, #4, #5 and #7 and will consider merging
> these. These cleanups account for most of the LOC reduction, and avoid
> most of the larger concerns.
>
> Also for patches like this, they really need testing on your end before
> I'll consider them merging. Compile testing alone for these types of
> locking changes is not enough, given the history of regressions with
> these types of cleanups.
OK. I'll look for those to show up in your tree, then? And work on
better dividing up of the remaining changes, and also minimize their
risk of causing regressions.
Regards -- Andy
prev parent reply other threads:[~2014-09-23 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1404171587-28845-1-git-send-email-agrover@redhat.com>
[not found] ` <20140729131511.GA30232@lst.de>
2014-09-13 19:55 ` [PATCHv3 0/8] target: Save memory on unused se_dev_entrys and se_luns Christoph Hellwig
2014-09-18 7:38 ` Nicholas A. Bellinger
2014-09-18 22:54 ` Andy Grover
2014-09-18 23:17 ` Nicholas A. Bellinger
2014-09-23 17:02 ` Andy Grover [this message]
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=5421A79F.9010003@redhat.com \
--to=agrover@redhat.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=target-devel@vger.kernel.org \
--cc=torvalds@linux-foundation.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