From: James Bottomley <James.Bottomley@suse.de>
To: Krishna Gudipati <kgudipat@Brocade.com>
Cc: Rob Evers <revers@redhat.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Jing Huang <huangj@Brocade.COM>,
Vinodh Ravindran <vravindr@Brocade.COM>,
Ramkumar Vadivelu <rvadivel@Brocade.COM>,
Akshay Mathur <amathur@brocade.com>,
Adapter Linux Open SRC Team
<adapter_linux_open_src_team@Brocade.COM>
Subject: RE: [PATCH 00/33] bfa: Brocade BFA FC SCSI driver v2.3.2.0 submission.
Date: Thu, 16 Sep 2010 10:34:23 -0400 [thread overview]
Message-ID: <1284647663.4603.16.camel@mulgrave.site> (raw)
In-Reply-To: <5EB1A55E180C914BBC1A49310B7629386690401D4B@HQ1-EXCH02.corp.brocade.com>
On Thu, 2010-09-16 at 07:32 -0700, Krishna Gudipati wrote:
> -----Original Message-----
> From: Rob Evers [mailto:revers@redhat.com]
>
> Your patch set seems to skip 1/33.
>
> I applied patch 2/33 to scsi-misc-2.6 that I cloned this morning.
> The last tag was v2.6.36-rc3
> I saw several instances of 'Reversed (or previously applied) patch
> detected', see below.
>
> Is there a particular tag I need to use?
>
> Thanks, Rob
>
> >>>
>
> Hi Rob,
>
> I did resend the patch1/33 twice, but it was never showing up in the linux-scsi mailing list.
> I am resending it to you and to the community again.
I think it might be too big ... I think we have a 400k limit on
linux-scsi. Patch 1/33 was 480k.
James
next prev parent reply other threads:[~2010-09-16 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 18:50 [PATCH 00/33] bfa: Brocade BFA FC SCSI driver v2.3.2.0 submission kgudipat
2010-09-16 14:10 ` Rob Evers
2010-09-16 14:32 ` Krishna Gudipati
2010-09-16 14:34 ` James Bottomley [this message]
2010-09-16 17:42 ` Krishna Gudipati
2010-09-16 17:47 ` James Bottomley
2010-09-16 14:50 ` Krishna Gudipati
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=1284647663.4603.16.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=adapter_linux_open_src_team@Brocade.COM \
--cc=amathur@brocade.com \
--cc=huangj@Brocade.COM \
--cc=kgudipat@Brocade.com \
--cc=linux-scsi@vger.kernel.org \
--cc=revers@redhat.com \
--cc=rvadivel@Brocade.COM \
--cc=vravindr@Brocade.COM \
/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.