From: Sam Ravnborg <sam@ravnborg.org>
To: Zeng Zhaoxiu <zhaoxiu.zeng@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH V2 01/30] bitops: add parity functions
Date: Wed, 6 Apr 2016 10:24:58 +0200 [thread overview]
Message-ID: <20160406082458.GA1202@ravnborg.org> (raw)
In-Reply-To: <57049FAF.4040804@gmail.com>
On Wed, Apr 06, 2016 at 01:33:35PM +0800, Zeng Zhaoxiu wrote:
> 在 2016年04月06日 03:04, Sam Ravnborg 写道:
> >On Tue, Apr 05, 2016 at 10:06:21AM +0800, Zeng Zhaoxiu wrote:
> >>From: Zhaoxiu Zeng <zhaoxiu.zeng@gmail.com>
> >>
> >>These patches provide generic and architecture-specific odd parity
> >>calculations.
> >Hi Zeng.
> >
> >Can you please fix your mail script.
> >I see only 1/30 (sent to linux-arch) - and patch looks mangeled (broken lines)
> >No mail was sent to sparclinux - but sparc was mentioned.
> >
> >git send-mail usually do the trick.
> >
> > Sam
>
> When I do "git send-email", I got:
> ...
> 5.7.14 JTibJDWdGxPcfa-E9KgtF-grMQl9w> Please log in via your web browser and
> 5.7.14 then try again.
> 5.7.14 Learn more at
> 5.7.14 https://support.google.com/mail/answer/78754 zp5sm464879pac.9 - gsmtp
> ...
>
> So I use thunderbird to send email, but the text wrap error.
Please try to search for "How to configure git send-email to use Gmail"
and follow the instructions given in some of the links.
Test with your own mail address before you send to a list.
Also linux-arch only saw 1/30 - make sure to address this too.
Sam
next prev parent reply other threads:[~2016-04-06 8:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 2:06 [PATCH V2 01/30] bitops: add parity functions Zeng Zhaoxiu
2016-04-05 2:06 ` Zeng Zhaoxiu
2016-04-05 19:04 ` Sam Ravnborg
2016-04-06 5:33 ` Zeng Zhaoxiu
2016-04-06 8:24 ` Sam Ravnborg [this message]
2016-04-06 8:24 ` Sam Ravnborg
2016-04-06 8:22 ` [PATCH v2 " zengzhaoxiu
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=20160406082458.GA1202@ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhaoxiu.zeng@gmail.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).