From: gang.chen.5i5j@gmail.com
To: Michal Hocko <mhocko@kernel.org>
Cc: gang.chen.5i5j@qq.com, Chen Gang <gang.chen.5i5j@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
kernel mailing list <linux-kernel@vger.kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
"riel@redhat.com" <riel@redhat.com>,
"sasha.levin@oracle.com" <sasha.levin@oracle.com>,
Linux Memory <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: mmap: Simplify the failure return working flow
Date: Mon, 24 Aug 2015 00:28:30 +0800 [thread overview]
Message-ID: <1440347310-17925-1-git-send-email-gang.chen.5i5j@gmail.com> (raw)
On 8/20/15 15:45, Michal Hocko wrote:
> On Thu 20-08-15 09:27:42, gchen gchen wrote:
> [...]
>> Yes, it is really peculiar, the reason is gmail is not stable in China.
>> I have to send mail in my hotmail address.
>>
>> But I still want to use my gmail as Signed-off-by, since I have already
>> used it, and also its name is a little formal than my hotmail.
>>
>> Welcome any ideas, suggestions and completions for it (e.g. if it is
>> necessary to let send mail and Signed-off-by mail be the same, I shall
>> try).
>
> You can do the following in your .git/config
>
> [user]
> name = YOUR_NAME_FOR_S-O-B
> email = YOUR_GMAIL_ADDRESS
> [sendemail]
> from = YOUR_STABLE_SENDER_ADDRESS
After trying, I guess, from = YOUR_GMAIL_ADDRESS
> envelopesender = YOUR_STABLE_SENDER_ADDRESS
> smtpserver = YOUR_STABLE_SMTP
>
> [user] part will be used for s-o-b and Author email while the sendemail
> will be used for git send-email to route the patch properly. If the two
> differ it will add From: user.name <user.email> as suggested by Andrew.
>
OK, thanks. I finished the configuration, and give a test (send and
receive test mail between my 2 mail address), it is OK.
I shall send patches in this way :-).
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2015-08-23 16:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 16:28 gang.chen.5i5j [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-23 16:20 [PATCH] mm: mmap: Simplify the failure return working flow gang.chen.5i5j
[not found] <55D5275D.7020406@hotmail.com>
[not found] ` <COL130-W46B6A43FC26795B43939E0B9660@phx.gbl>
[not found] ` <55D52C9A.5060705@hotmail.com>
2015-08-20 1:26 ` gchen gchen
[not found] ` <55D52CDE.8060700@hotmail.com>
2015-08-20 1:27 ` gchen gchen
2015-08-20 7:45 ` Michal Hocko
[not found] ` <55D593C2.3040105@hotmail.com>
2015-08-20 8:48 ` gchen gchen
2015-08-23 17:28 ` Chen Gang
2015-08-18 22:27 Chen Gang
2015-08-18 22:57 ` Andrew Morton
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=1440347310-17925-1-git-send-email-gang.chen.5i5j@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gang.chen.5i5j@qq.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=riel@redhat.com \
--cc=sasha.levin@oracle.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).