linux-kernel - Re: [PATCH 0/5] mtip32xx: Add support for device status and some optimitizations

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 06 Apr 2012 11:39:38 -0600
From:	Jens Axboe <axboe@...nel.dk>
To:	Asai Thambi S P <asamymuthupa@...ron.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Sam Bradshaw <sbradshaw@...ron.com>
Subject: Re: [PATCH 0/5] mtip32xx: Add support for device status and some
 optimitizations

On 2012-04-06 11:38, Asai Thambi S P wrote:
> On 4/5/2012 5:21 PM, Jens Axboe wrote:
> 
>> On 2012-04-05 14:59, Asai Thambi S P wrote:
>>>
>>> This patchset adds support for new sysfs entry 'status', fix in restart port,
>>> and some optimizations like merging various flag variables. 
>>>
>>> Asai Thambi S P (5):
>>>   mtip32xx: Add new bitwise flag 'dd_flag' and make set comp_time as
>>>     common
>>>   mtip32xx: Add new sysfs entry 'status' and fix restart port
>>>   mtip32xx: Shorten macro names
>>>   mtip32xx: handling of commands in various scenarios
>>>   mtip32xx: dump tagmap on failure
>>>
>>>  drivers/block/mtip32xx/mtip32xx.c |  844 +++++++++++++++++++++++++++++--------
>>>  drivers/block/mtip32xx/mtip32xx.h |   58 ++-
>>>  2 files changed, 702 insertions(+), 200 deletions(-)
>>
>> These are not applying to for-3.4/drivers, so I can't apply them as-is.
>>
> 
> 
> Sorry, patches were based on master. I will re-base for-3.4/drivers

Thanks, there's a mtip32xx patch in there already, so that's probably
what is causing the issue.

-- 
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/