From: Tirumala Marri <tmarri@apm.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-raid@vger.kernel.org, herbert@gondor.hengli.com.au,
linuxppc-dev@lists.ozlabs.org, linux-crypto@vger.kernel.org,
yur@emcraft.com
Subject: RE: [PATCH v1 1/4] PPC4xx: Generalizing ADMA driver modifications
Date: Thu, 23 Sep 2010 15:44:41 -0700 [thread overview]
Message-ID: <fe45b421a909d749a6cf583426a1ce6d@mail.gmail.com> (raw)
In-Reply-To: <4C9BD6DC.3070707@intel.com>
>
> Did you look at this changelog before sending? It just deletes 4000
> lines of code??
[Marri] The reason I have to send it in different file is the size of the
patch.
There seem to be issue with patch sizes 200k or more.
next prev parent reply other threads:[~2010-09-23 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 22:10 [PATCH v1 1/4] PPC4xx: Generalizing ADMA driver modifications tmarri
2010-09-23 22:38 ` Dan Williams
2010-09-23 22:44 ` Tirumala Marri [this message]
2010-09-23 22:51 ` Dan Williams
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=fe45b421a909d749a6cf583426a1ce6d@mail.gmail.com \
--to=tmarri@apm.com \
--cc=dan.j.williams@intel.com \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=yur@emcraft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).