From: "Christian König" <christian.koenig@amd.com>
To: Greg KH <greg@kroah.com>, Chunming Zhou <David1.Zhou@amd.com>
Cc: <stable@vger.kernel.org>
Subject: Re: [PATCH] drm/amdgpu: fix the lost duplicates checking
Date: Mon, 7 Dec 2015 14:40:31 +0100 [thread overview]
Message-ID: <56658C4F.3030306@amd.com> (raw)
In-Reply-To: <20151207121518.GB25909@kroah.com>
On 07.12.2015 13:15, Greg KH wrote:
> <formletter>
>
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree. Please read Documentation/stable_kernel_rules.txt
> for how to do this properly.
>
> </formletter>
Sorry that's my fault. I noted that we need to add a Cc:
stable@vger.kernel.org tag to the patch before pushing it upstream and
the David obviously misunderstood that he should send it as a mail to
stable@vger.kernel.org.
Please ignore this mail and *DON'T* add it to the stable tree. This
patch should make it's normal way though into the kernel through the
subsystem maintainer.
Best regards,
Christian.
prev parent reply other threads:[~2015-12-07 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 9:08 [PATCH] drm/amdgpu: fix the lost duplicates checking Chunming Zhou
2015-12-07 12:15 ` Greg KH
2015-12-07 13:40 ` Christian König [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=56658C4F.3030306@amd.com \
--to=christian.koenig@amd.com \
--cc=David1.Zhou@amd.com \
--cc=greg@kroah.com \
--cc=stable@vger.kernel.org \
/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).