> From: Chen Gang <[email protected]> > Date: Thu, 9 Jul 2015 02:44:26 +0200 >On 07/07/2015 08:05 PM, Hans-Peter Nilsson wrote: > > As a collateral, can I have an "upstream" GIT (slug and) commit > > id I can use to compile a CRIS v10 kernel, possibly modulo this > > issue? I need to use the kernel as a test-case for a gcc issue. > > I'll use Segher Boessenkool "buildall" kernelbuild scripts, but > > I'm missing a compilable kernel commit-id. (No, I haven't > > actually followed my own advice but by your email I'm guessing > > CRIS v10 isn't currently compilable.) > > > > Excuse me, I am not quite understand your meaning, welcome additional > details explanations.
I'll use other words and less details: I have a gcc-bug for CRIS v10 and CRIS v32 to investigate and need to use the kernel as a test-case. So, I need to check out kernel sources that I know will compile, as I know there are kernel issues with the CRIS port(s) from time to time. I don't usually compile the kernel. > And for me, hope the details below are useful for what you said above ( > but I am not quite sure). > > - I use the linux-next git tree which everyone can "git clone": > "git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git", > and I often use "git remote update" to get the latest release. > > - With the related patches I have sent, the "git tag" next-20150702 can > pass allmodconfig with the cross raw compiler (allmodconfig selects > CRIS v10). Thank you, the git and the tag is exactly the information I need. brgds, H-P -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
