From: Greg KH <gregkh@linuxfoundation.org>
To: yong w <yongw.pur@gmail.com>
Cc: jaewon31.kim@samsung.com, linux-kernel@vger.kernel.org,
mhocko@kernel.org, stable@vger.kernel.org,
wang.yong12@zte.com.cn
Subject: Re: [PATCH v2 stable-4.19 0/3] page_alloc: consider highatomic reserve in watermark fast backports to 4.19
Date: Mon, 10 Oct 2022 17:58:45 +0200 [thread overview]
Message-ID: <Y0RBNTQnYpoF1r7w@kroah.com> (raw)
In-Reply-To: <CAOH5QeAX0NzO2mXqBbMRYGMzNMTAq4H1r9r_AFWC2Fj=MNWwiw@mail.gmail.com>
On Mon, Oct 10, 2022 at 11:47:30PM +0800, yong w wrote:
> Greg KH <gregkh@linuxfoundation.org> 于2022年10月8日周六 00:40写道：
> >
> > A: http://en.wikipedia.org/wiki/Top_post
> > Q: Were do I find info about this thing called top-posting?
> > A: Because it messes up the order in which people normally read text.
> > Q: Why is top-posting such a bad thing?
> > A: Top-posting.
> > Q: What is the most annoying thing in e-mail?
> >
> > A: No.
> > Q: Should I include quotations after my reply?
> >
> > http://daringfireball.net/2007/07/on_top
> >
> >
> > On Fri, Oct 07, 2022 at 04:53:50PM +0800, yong w wrote:
> > > Is it ok to add my signed-off-by? my signed-off-by is as follows:
> > >
> > > Signed-off-by: wangyong <wang.yong12@zte.com.cn>
> >
> > For obvious reasons, I can not take that from a random gmail account
> > (nor should ZTE want me to do that.)
> >
> > Please fix up your email systems and do this properly and send the
> > series again.
> >
> > thanks,
> >
> > greg k-h
>
> Sorry, our mail system cannot send external mail for some reason.
Sorry, then I can not attribute anything to your company. It has
already been warned that it can not continue to contribute to the Linux
kernel and some of your gmail "aliases" have been banned from the
mailing lists.
Please fix your email system so that you can properly contribute to
Linux.
> And this is my email, I can receive an email and reply to it.
Yes, but I have no proof that your ZTE email is correct, only that this
is a random gmail.com address :(
What would you do if you were in my situation?
Please work with your IT group to fix their email systems.
good luck,
greg k-h
next prev parent reply other threads:[~2022-10-10 15:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 13:09 [PATCH v4] page_alloc: consider highatomic reserve in watermark fast yong
2022-09-13 13:54 ` Greg KH
2022-09-14 0:46 ` yong w
2022-09-16 9:40 ` Greg KH
2022-09-16 17:05 ` [PATCH stable-4.19 0/3] page_alloc: consider highatomic reserve in watermark fast backports to 4.19 wangyong
2022-09-16 17:05 ` [PATCH 1/3] mm/page_alloc: use ac->high_zoneidx for classzone_idx wangyong
2022-09-16 17:09 ` kernel test robot
2022-09-16 17:05 ` [PATCH 2/3] page_alloc: consider highatomic reserve in watermark fast wangyong
2022-09-16 17:05 ` [PATCH 3/3] page_alloc: fix invalid watermark check on a negative value wangyong
2022-09-20 17:41 ` [PATCH stable-4.19 0/3] page_alloc: consider highatomic reserve in watermark fast backports to 4.19 Greg KH
2022-09-25 10:35 ` [PATCH v2 " wangyong
2022-09-25 10:35 ` [PATCH v2 stable-4.19 1/3] mm/page_alloc: use ac->high_zoneidx for classzone_idx wangyong
2022-09-25 10:36 ` kernel test robot
2022-09-25 11:00 ` Greg KH
2022-09-25 14:32 ` yong w
2022-09-26 6:46 ` Greg KH
2022-09-25 10:35 ` [PATCH v2 stable-4.19 2/3] page_alloc: consider highatomic reserve in watermark fast wangyong
2022-09-25 10:35 ` [PATCH v2 stable-4.19 3/3] page_alloc: fix invalid watermark check on a negative value wangyong
2022-10-02 15:37 ` [PATCH v2 stable-4.19 0/3] page_alloc: consider highatomic reserve in watermark fast backports to 4.19 Greg KH
[not found] ` <CAOH5QeB2EqpqQd6fw-P199w8K8-3QNv_t-u_Wn1BLnfaSscmCg@mail.gmail.com>
2022-10-07 16:41 ` Greg KH
2022-10-10 15:47 ` yong w
2022-10-10 15:58 ` Greg KH [this message]
2022-09-18 1:41 ` [PATCH v4] page_alloc: consider highatomic reserve in watermark fast Jaewon Kim
2022-09-19 13:21 ` yong w
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=Y0RBNTQnYpoF1r7w@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jaewon31.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wang.yong12@zte.com.cn \
--cc=yongw.pur@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