* Re: [PATCH] drm: Loongson-3 doesn't fully support wc memory
[not found] ` <CADnq5_OyS_pCu-4wW5uFpnr5kvqkHK5uPdmBKgHHmfZ-dOdXvw@mail.gmail.com>
@ 2016-04-20 6:18 ` Huacai Chen
2016-04-20 6:49 ` Greg KH
0 siblings, 1 reply; 3+ messages in thread
From: Huacai Chen @ 2016-04-20 6:18 UTC (permalink / raw)
To: Alex Deucher, stable
Cc: Linux MIPS Mailing List, Maling list - DRI developers
Cc: stable@vger.kernel.org
On Tue, Apr 19, 2016 at 9:53 PM, Alex Deucher <alexdeucher@gmail.com> wrote:
> On Tue, Apr 19, 2016 at 7:19 AM, Huacai Chen <chenhc@lemote.com> wrote:
>> Signed-off-by: Huacai Chen <chenhc@lemote.com>
>
> Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
>
>> ---
>> include/drm/drm_cache.h | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/include/drm/drm_cache.h b/include/drm/drm_cache.h
>> index 461a055..cebecff 100644
>> --- a/include/drm/drm_cache.h
>> +++ b/include/drm/drm_cache.h
>> @@ -39,6 +39,8 @@ static inline bool drm_arch_can_wc_memory(void)
>> {
>> #if defined(CONFIG_PPC) && !defined(CONFIG_NOT_COHERENT_CACHE)
>> return false;
>> +#elif defined(CONFIG_MIPS) && defined(CONFIG_CPU_LOONGSON3)
>> + return false;
>> #else
>> return true;
>> #endif
>> --
>> 2.7.0
>>
>>
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] drm: Loongson-3 doesn't fully support wc memory
2016-04-20 6:18 ` [PATCH] drm: Loongson-3 doesn't fully support wc memory Huacai Chen
@ 2016-04-20 6:49 ` Greg KH
2016-04-20 11:24 ` Daniel Vetter
0 siblings, 1 reply; 3+ messages in thread
From: Greg KH @ 2016-04-20 6:49 UTC (permalink / raw)
To: Huacai Chen
Cc: Alex Deucher, stable, Linux MIPS Mailing List,
Maling list - DRI developers
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>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] drm: Loongson-3 doesn't fully support wc memory
2016-04-20 6:49 ` Greg KH
@ 2016-04-20 11:24 ` Daniel Vetter
0 siblings, 0 replies; 3+ messages in thread
From: Daniel Vetter @ 2016-04-20 11:24 UTC (permalink / raw)
To: Greg KH
Cc: Huacai Chen, Linux MIPS Mailing List,
Maling list - DRI developers, stable
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-04-20 11:24 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1461064751-17873-1-git-send-email-chenhc@lemote.com>
[not found] ` <CADnq5_OyS_pCu-4wW5uFpnr5kvqkHK5uPdmBKgHHmfZ-dOdXvw@mail.gmail.com>
2016-04-20 6:18 ` [PATCH] drm: Loongson-3 doesn't fully support wc memory Huacai Chen
2016-04-20 6:49 ` Greg KH
2016-04-20 11:24 ` Daniel Vetter
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).