Re: [PATCH] backports: add definitions S32_MAX and S32_MIN

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


> I create a package nightly for our internal tree and wireless-testing
> and build for couple of target kernels to run some wifi tests on
> target systems. So I tend to hit issues pretty soon. Not covering all
> target kernels though.

Ok, that's nice. I'm torn between doing something that runs on our
existing infrastructure (easy, but internal) or building some kind of
infrastructure, likely on the build box we have from the LF... that's
harder but accessible to people other than me.

Or are there any alternatives? Perhaps if I put the scripts upstream
then it doesn't matter that I might actually be running it on our
internal infrastructure, since anyone can just take the scripts and run

To unsubscribe from this list: send the line "unsubscribe backports" in

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux