From: Daniel Vetter <daniel@ffwll.ch>
To: Greg KH <greg@kroah.com>
Cc: Huacai Chen <chenhc@lemote.com>,
Linux MIPS Mailing List <linux-mips@linux-mips.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH] drm: Loongson-3 doesn't fully support wc memory
Date: Wed, 20 Apr 2016 13:24:09 +0200 [thread overview]
Message-ID: <20160420112409.GN2510@phenom.ffwll.local> (raw)
In-Reply-To: <20160420064923.GA698@kroah.com>
On Wed, Apr 20, 2016 at 03:49:23PM +0900, Greg KH wrote:
> On Wed, Apr 20, 2016 at 02:18:20PM +0800, Huacai Chen wrote:
> > Cc: stable@vger.kernel.org
>
> <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>
Not sure what exactly your script latched onto, but at least in the drm
subsystem it's pretty common to remind maintainers with a reply just
containing
Cc: stable@vger.kernel.org
that they need to add that to the patch when applying. Often combined with
an r-b/a-b tag. And Damien is working to teach patchwork to auto-add
those, so yeah it's indeed the right way to submit a patch for stable. At
least here ;-)
Cheers, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: Greg KH <greg@kroah.com>
Cc: Huacai Chen <chenhc@lemote.com>, stable <stable@vger.kernel.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
Linux MIPS Mailing List <linux-mips@linux-mips.org>
Subject: Re: [PATCH] drm: Loongson-3 doesn't fully support wc memory
Date: Wed, 20 Apr 2016 13:24:09 +0200 [thread overview]
Message-ID: <20160420112409.GN2510@phenom.ffwll.local> (raw)
In-Reply-To: <20160420064923.GA698@kroah.com>
On Wed, Apr 20, 2016 at 03:49:23PM +0900, Greg KH wrote:
> On Wed, Apr 20, 2016 at 02:18:20PM +0800, Huacai Chen wrote:
> > Cc: stable@vger.kernel.org
>
> <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>
Not sure what exactly your script latched onto, but at least in the drm
subsystem it's pretty common to remind maintainers with a reply just
containing
Cc: stable@vger.kernel.org
that they need to add that to the patch when applying. Often combined with
an r-b/a-b tag. And Damien is working to teach patchwork to auto-add
those, so yeah it's indeed the right way to submit a patch for stable. At
least here ;-)
Cheers, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-04-20 11:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 11:19 [PATCH] drm: Loongson-3 doesn't fully support wc memory Huacai Chen
2016-04-19 13:53 ` Alex Deucher
2016-04-19 13:53 ` Alex Deucher
2016-04-20 6:18 ` Huacai Chen
2016-04-20 6:18 ` Huacai Chen
2016-04-20 6:49 ` Greg KH
2016-04-20 11:24 ` Daniel Vetter [this message]
2016-04-20 11:24 ` Daniel Vetter
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=20160420112409.GN2510@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chenhc@lemote.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=greg@kroah.com \
--cc=linux-mips@linux-mips.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.