From: Chris Ball <cjb@laptop.org>
To: Zhu Richard-R65037 <R65037@freescale.com>
Cc: Zhang Lily-R58066 <R58066@freescale.com>,
"root@udp161639uds.ap.freescale.net"
<root@udp161639uds.ap.freescale.net>,
ReviewList Linux-LNXREVLI <LNXREVLI@freescale.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: Re:[lnxrevli] [REVIEW 2/2] ENGR0000137838 SDHCI Some eMMC cards can't workwell in our BSP
Date: Tue, 11 Jan 2011 02:22:30 +0000 [thread overview]
Message-ID: <20110111022229.GB9534@void.printf.net> (raw)
In-Reply-To: <010C9052C42A00499CE76D637FA5EE9004756C@039-SN1MPN1-001.039d.mgd.msft.net>
Hi Richard,
On Tue, Jan 11, 2011 at 02:17:08AM +0000, Zhu Richard-R65037 wrote:
> Hi Chris:
> I keep all the info of the original patch into my local patch.
> The script the pull-tool used by us send out the emails to all the sign-off email address,
> When I used this tool to push the local patch into our mainline.
> Sorry to bring any inconvenience to you.
Please modify the script so that it does not send mail to the people
in the Signed-off chain, or at least so that it never sends mail to
linux-mmc@. The fact that you're importing a patch locally is off-topic
for the list.
Thanks,
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2011-01-11 2:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 2:02 [REVIEW 2/2] ENGR0000137838 SDHCI Some eMMC cards can't work well in our BSP Richard Zhu
2011-01-11 2:07 ` Chris Ball
[not found] ` <1.10.2011-mgd.freescale.com-30-6343028328831767454500-3831@freescale.com>
2011-01-11 2:17 ` Re:[lnxrevli] [REVIEW 2/2] ENGR0000137838 SDHCI Some eMMC cards can't workwell " Zhu Richard-R65037
2011-01-11 2:22 ` Chris Ball [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=20110111022229.GB9534@void.printf.net \
--to=cjb@laptop.org \
--cc=LNXREVLI@freescale.com \
--cc=R58066@freescale.com \
--cc=R65037@freescale.com \
--cc=linux-mmc@vger.kernel.org \
--cc=root@udp161639uds.ap.freescale.net \
/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