On 01/16/2013 12:56 PM, Jeremy C. Andrus wrote: > From: "Jeremy C. Andrus" <jeremya@xxxxxxxxxxxxxxx> > > In the course of my research here at Columbia University, I have been > doing some kernel development on the Google Nexus 7 device. I took the > time to address most of the compile-time warnings while building the > Tegra kernel tree using the cross-compiler shipped with Android > (gcc-4.7), and in doing so I came across a few minor issues. > > This RFC series addresses several minor bugs that I was able to fix > while suppressing compile warnings. Not knowing exactly where > to send the patches, I decided to send them primarily to the Tegra > list serv in hopes that they will find their way to the correct place. > > All 5 patches apply cleanly the kernel/tegra repository hosted by > Google. I used the commit hash referenced in the Android device tree > git logs as my HEAD revision: 22b4fcde206e96f57bf0a111403fc3d75532918a > I belive that this is the revision which corresponds to the prebuilt > kernel provided in the Jelly Bean release. I honestly don't know where you should send these patches. I've CC'd Colin Cross who works on Android in case he can clue us in. I assume there's a Gerrit instance somewhere for Android that you need to push these into... Laxman, can you please check if any of these patches should be applied to our internal/downstream kernels? Jeremy, do patches 3 or 4 need to be applied to the mainline kernel? It may be useful for you to resend those directly to the relevant upstream subsystem maintainers, after rebasing them onto the latest upstream code. See Documentation/SubmittingPatches in the mainline kernel. Thanks for the contributions! -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
