Am Mittwoch, 21. Mai 2014, 18:39:26 schrieb Vasily Khoruzhick: > On Wed, May 21, 2014 at 6:29 PM, Heiko Stübner <heiko@xxxxxxxxx> wrote: > > Am Mittwoch, 21. Mai 2014, 17:07:47 schrieb Tomasz Figa: > >> On 21.05.2014 16:53, Vasily Khoruzhick wrote: > >> > On Wed, May 21, 2014 at 4:28 PM, Tomasz Figa <t.figa@xxxxxxxxxxx> wrote: > >> >> Please remember to keep linux-samsung-soc ML on Cc when sending > >> >> patches > >> >> related to Samsung platforms. It is essential to let Samsung people > >> >> review them. > >> > > >> > Ok, I'll keep it in mind. I've just checked and get_maintainer.pl > >> > outputs linux-samsung-soc ML for these > >> > patches. I've omitted it occasionally, because it wasn't necessary to > >> > keep it in CC back in 2011 > >> > (year of my last sound-related patch for s3c24xx). > >> > > >> >> Please resend the series with this in mind. > >> > > >> > Is it really necessary? This patch is supposed to go through ASoC > >> > tree, not through Samsung's. > >> > And I really doubt that Samsung guys test kernel for s3c24xx boards > >> > nowadays. > >> > >> Maybe not test, but at least review the code. Also there might be other > >> people following that list that might be interested in looking at this > >> series, while not subscribed to alsa-devel - I can name at least Heiko > >> Stübner, who should be able to test it on further s3c24xx-based boards. > > > > Sadly, I don't have a working sound setup on my 2 s3c boards. > > What are they btw? Is it too time-consuming to make sound working on them? > It would be nice if anyone except me could test these patches. Openmoko Freerunner (S3C2440) where there may be sound reachable someway and a "Oyo" ebook-reader (S3C2416) whose i2s is I think compatible with the s3c64xx instead of the s3c24xx ones and with a completely unsupported codec. But in general I'm fairly confident that if you hear sounds on your device your conversion would be fine test-wise :-) Heiko -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |