Re: [PATCH v2 0/10] megaraid_sas : Updates for scsi for-next

[James Bottomley <James.Bottomley@HansenPartnership.com>]

On Thu, 2015-08-20 at 18:43 +0530, Sumit.Saxena@avagotech.com wrote:
> MegaRaid driver changes. This patch set is resent based on feedback received by Martin Petersen.
> Please consider this patch set for next kernel release.
> 
> Signed-off-by: Sumit Saxena <sumit.saxena@avagotech.com>
> Signed-off-by: Kashyap Desai <kashyap.desai@avagotech.com>
> ---
> [PATCH v2 00/10] megaraid_sas : Updates for scsi for-next.
> [PATCH v2 01/10] megaraid_sas : Synchronize driver headers with firmware APIs.
> [PATCH v2 02/10] megaraid_sas : Increase timeout to 60 secs for abort frames during shutdown.
> [PATCH v2 03/10] megaraid_sas : Jbod sequence number support.
> [PATCH v2 04/10] megaraid_sas : Code cleanup-use local variable drv_ops inside megasas_ioc_init_fusion.
> [PATCH v2 05/10] megaraid_sas : Support for max_io_size 1MB.
> [PATCH v2 06/10] megaraid_sas : Chip reset if driver fail to bring ioc ready.
> [PATCH v2 07/10] megaraid_sas : Print critical fw event message.
> [PATCH v2 08/10] megaraid_sas : Fix validHandles check in io path.
> [PATCH v2 09/10] megaraid_sas : Code refactor for use of requestorId.
> [PATCH v2 10/10] megaraid_sas : Version upgrade.

I'm getting a ton of rejects in this series because of

commit da0dc9fb4e6b0ad5a947c27a3c48985f6a2377eb
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Tue Jul 7 15:52:45 2015 -0500

    megaraid_sas: fix whitespace errors

Please fix.

Useful rules of thumb are don't ack whitespace patches because they
inevitably cause this type of issue.  If you do decide to ack, make sure
you don't cause conflicts with your own outstanding patches.

James