From: Chuanxiao <chuanxiao.dong@gmail.com>
To: David Woodhouse <David.Woodhouse@intel.com>
Cc: chuanxiao.dong@intel.com, hang.yuan@intel.com,
linux-mtd@lists.infradead.org, yunpeng.gao@intel.com,
dedekind1@gmail.com
Subject: Re: [PATCH V2 1/5]nand/denali Clean up all white spaces in code indent
Date: Fri, 6 Aug 2010 00:09:52 +0800 [thread overview]
Message-ID: <20100805160951.GA3160@infernal> (raw)
In-Reply-To: <1281022802.8720.16.camel@localhost>
On Thu, Aug 05, 2010 at 04:40:02PM +0100, David Woodhouse wrote:
>On Thu, 2010-08-05 at 16:29 +0100, Chuanxiao wrote:
>> On Thu, Aug 05, 2010 at 04:11:58PM +0100, David Woodhouse wrote:
>> >On Thu, 2010-08-05 at 16:06 +0100, Chuanxiao wrote:
>> >> Hi,
>> >> I have changed the outlook mail cliet to be linux mutt client and use my
>> >> personal gmail to submit patches.
>> >> Here are 5 new patches to fix nand/denali check patch errors. The other
>> >> 4 patches will be sent out after this mail.
>> >> Thanks for your review.
>> >
>> >Apply? [y]es/[n]o/[e]dit/[v]iew patch/[a]ccept all y
>> >Applying: nand/denali Clean up all white spaces in code indent
>> >error: patch failed: drivers/mtd/nand/denali.c:29
>> >error: drivers/mtd/nand/denali.c: patch does not apply
>> >Patch failed at 0001 nand/denali Clean up all white spaces in code indent
>> >
>> >
>> >Are you *really* sending this stuff to yourself first, and checking that
>> >it applies *before* you try sending mail to anyone else?
>>
>> Before I send these patches to mail list I have sent them to myself
>> first and applies all of them, but not using "intel.com" account.
>> I have already using mutt as mail client.
>> I have been tortured by "intel.com" mail for several days and found that
>> the email I received through "intel.com" account lost tab and some white
>> spaces but no problems recevied through my personal mail "gmail.com".
>> I don't understand how this happend.
>> So David, can you try the patches get from linux-mtd mail list, not from
>> your "intel.com" account?
>
>Yes, the copy I received through my external email is working fine.
>Sorry for not checking that before -- I thought the issues with Intel
>mail servers corrupting email were long since fixed.
>
>Please don't use my @intel.com mail address for *anything* that needs to
>survive intact; please use dwmw2@infradead.org instead.
OK. Thanks for your understanding. I will send patches to @infradead.org
mail list insteand.
>
>I've now applied your patches. Are there more to come?
There are 2 more patches I will send out later and if there is no
problem I will send more tomorrow.
Thank you, David.
>
>--
>David Woodhouse Open Source Technology Centre
>David.Woodhouse@intel.com Intel Corporation
>
prev parent reply other threads:[~2010-08-05 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 15:06 [PATCH V2 1/5]nand/denali Clean up all white spaces in code indent Chuanxiao
2010-08-05 15:11 ` David Woodhouse
2010-08-05 15:29 ` Chuanxiao
2010-08-05 15:40 ` David Woodhouse
2010-08-05 16:09 ` Chuanxiao [this message]
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=20100805160951.GA3160@infernal \
--to=chuanxiao.dong@gmail.com \
--cc=David.Woodhouse@intel.com \
--cc=chuanxiao.dong@intel.com \
--cc=dedekind1@gmail.com \
--cc=hang.yuan@intel.com \
--cc=linux-mtd@lists.infradead.org \
--cc=yunpeng.gao@intel.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.