Comment 23 for bug 1500156

Revision history for this message
In , Tiwai-r (tiwai-r) wrote :

(In reply to comment #3)
> I am not a kernel developer and so I'm not sure how to build r592.c with the
> patch, however, I would be happy to test it if somebody else would build it for
> me. Alternatively, if its simple to do, then please provide some instructions
> and I will attempt to build it.

Yes, you should learn how to build a kernel and a patched module. There are a few good ways. I'll give some brief instructions later.

> Also, the following is from a post at:
>
> https://forums.opensuse.org/showthread.php/494706-openSUSE-13-1-KDE-inconsistant-resume-from-Suspend-to-RAM?p=2661131#post2661131
>
> Quoting Romanator: "The most recent openSUSE kernel (3.11.10-21-desktop)
> Makefile for the r592.c from Maxim Levitsky is from 2010. His final patch
> wasn't submitted until Jan. 8, 2011. <snip> Ask the openSUSE kernel devs to
> look at and backport patch #5b945a6 from this link:
> https://gitorious.org/ricoh-kernel/ricoh-kernel.git ".
>
> So, it doesn't look like the OpenSUSE kernel has the most recent r592 driver...

You're testing 3.15 and 3.16, so the above statement doesn't fit at all.

> Also, there is a good bit of recent activity by the r592 developer, Maxim
> Levitsky, on this exact same bug at Red Hat's Bugzilla site here:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1119361
>
> The bottom line is that someone needs to make sure that OpenSUSE is using the
> most recent version of r592.c.

No, r592 developer has to submit the fix to the upstream at first. This is the golden rule. In general, we take *only* the upstream fix (or the patch that is promised to upstream) to openSUSE kernels.

If there is a problem of upstreaming, put me in Cc in chain, so that I can assist for it.