All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Henzl <thenzl@redhat.com>
To: adam radford <aradford@gmail.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	Bo.Yang@lsi.com, James Bottomley <James.Bottomley@suse.de>
Subject: Re: [PATCH 7/11]: megaraid_sas: Add MegaRAID 9265/9285 specific functions: megaraid_sas_fusion.c
Date: Fri, 17 Dec 2010 11:42:39 +0100	[thread overview]
Message-ID: <4D0B3E9F.5000101@redhat.com> (raw)
In-Reply-To: <AANLkTin5=YL2mQxtGKQUTRCvnb2N29B32+J2ds8t-xPP@mail.gmail.com>

On 12/16/2010 06:13 PM, adam radford wrote:
> On Thu, Dec 16, 2010 at 8:58 AM, adam radford <aradford@gmail.com> wrote:
>   
>> On Thu, Dec 16, 2010 at 5:57 AM, Tomas Henzl <thenzl@redhat.com> wrote:
>>     
>>> Hi Adam, Bo,
>>>
>>> The function megasas_fusion_ocr_wq seems to be used already in patch 6/11
>>> and declared in 7/11 - this breaks bisectability.
>>>
>>> Further my compiler complains about a large frame size.
>>> Probably the 'struct scsi_device dev' is too large to be on stack.
>>> make checkstack
>>> ...
>>> 0x000090f4 megasas_fusion_ocr_wq [megaraid_sas]:        1696
>>>
>>>       
>> Tomas,
>>
>> Thanks, we will fix this and repost patches 6 thru 10.
>>
>> -Adam
>>
>>     
> Tomas,
>
> Actually, if you look the patch 6, we put a note in there, that
> patches 6 thru 10 must be applied 'at once' for the build to work:
>
> "Note: Patches 6 thru 10 have to be applied at once in order to build."
>   
I'm not sure if git-bisect can understand this.

> This has been allowed on this list before.  Otherwise, we would have a
> very large patch while turning on the new support for this controller,
> making the patch less review-able by the community.
>   
If the maintainer accepts this, than I'm fine too. 

> I will look into and fix the large frame size compile issue you are
> seeing and re-post the appropriate patches.
>   
Thanks.
Tomas

> -Adam
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   


  reply	other threads:[~2010-12-17 10:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15  3:04 [PATCH 7/11]: megaraid_sas: Add MegaRAID 9265/9285 specific functions: megaraid_sas_fusion.c adam radford
2010-12-16 13:57 ` Tomas Henzl
2010-12-16 16:58   ` adam radford
2010-12-16 17:13     ` adam radford
2010-12-17 10:42       ` Tomas Henzl [this message]
2010-12-17 13:13         ` James Bottomley
2010-12-17 17:30           ` adam radford
2010-12-17 17:46             ` adam radford
2010-12-21 20:28 ` Christoph Hellwig
2010-12-21 20:53   ` adam radford

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=4D0B3E9F.5000101@redhat.com \
    --to=thenzl@redhat.com \
    --cc=Bo.Yang@lsi.com \
    --cc=James.Bottomley@suse.de \
    --cc=aradford@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.