On Thu, Aug 22, 2019 at 01:02:05PM -0700, 'Nick Desaulniers' via Clang Built Linux wrote: > On Thu, Aug 22, 2019 at 11:30 AM Nathan Huckleberry <nh...@google.com> wrote: > > > > The stackframe setup when compiled with clang is different. > > Since the stack unwinder expects the gcc stackframe setup it > > fails to print backtraces. This patch adds support for the > > clang stackframe setup. > > > > Link: https://github.com/ClangBuiltLinux/linux/issues/35 > > Cc: clang-built-li...@googlegroups.com > > Suggested-by: Tri Vo <tr...@google.com> > > Signed-off-by: Nathan Huckleberry <nh...@google.com> > > Tested-by: Nick Desaulniers <ndesaulni...@google.com> > > Great, thanks for following up on the suggestions from code review. > Since this is going to go up via the arm tree, which has its own > process, please add my: > Reviewed-by: Nick Desaulniers <ndesaulni...@google.com> > to the commit message, then submit the patch to the maintainer's patch > tracking system: > https://www.armlinux.org.uk/developer/patches/info.php > (create a login, sign in, then visit: > https://www.armlinux.org.uk/developer/patches/add.php . I think the > correct thing is to put the first line of the commit in the summary > field, next/master as the kernel version (I applied/tested off of > -next), then the rest of the commit message body in the Patch Notes > field. Make sure to attach the patch file. Finally, it should appear > at https://www.armlinux.org.uk/developer/patches/section.php?section=0 > I think within 24hrs).
Also for the record, I came across this a couple of months ago, Catalin Marinas had a git config alias that could be used for sending one patch to the patches email address so that you don't have to muck around the web interface: https://lore.kernel.org/lkml/20190624144924.ge29...@arrakis.emea.arm.com/ Web interface works fine but I prefer everything via the command line :) Cheers, Nathan
