From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Abhijit Ayarekar <abhijit.ayarekar@caviumnetworks.com>
Cc: ast@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add -target to clang switch while cross compiling.
Date: Thu, 12 Oct 2017 18:14:01 -0700 [thread overview]
Message-ID: <20171013011359.tyhynrjghe2krxec@ast-mbp> (raw)
In-Reply-To: <1507852723-24677-1-git-send-email-abhijit.ayarekar@caviumnetworks.com>
On Thu, Oct 12, 2017 at 04:58:43PM -0700, Abhijit Ayarekar wrote:
> Update to llvm excludes assembly instructions.
> llvm git revision is below
>
> commit 2865ab6996164e7854d55c9e21c065fad7c26569
> Author: Yonghong Song <yhs@fb.com>
> Date: Mon Sep 18 23:29:36 2017 +0000
>
> bpf: add inline-asm support
>
> Signed-off-by: Yonghong Song <yhs@fb.com>
> Acked-by: Alexei Starovoitov <ast@kernel.org>
>
> git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@313593 91177308-0d34-0410-b5e6-96231b3b80d8
correct way to reference a commit is
commit 81eb8447daae ("ipv6: take care of rt6_stats")
Also I think git-svn-id link is broken. I'm not sure why llvm keeps
adding it to commits. Kernel's git history doesn't need them.
So just mention llvm commit in kernel's cannonical way and
mention that it will be part of llvm release 6.0
next prev parent reply other threads:[~2017-10-13 1:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 20:45 [PATCH] Add -target to clang switches while cross compiling Abhijit Ayarekar
2017-10-12 22:23 ` Alexei Starovoitov
2017-10-12 22:43 ` Abhijit Ayarekar
2017-10-12 23:16 ` Alexei Starovoitov
2017-10-12 23:58 ` [PATCH] Add -target to clang switch " Abhijit Ayarekar
2017-10-13 1:14 ` Alexei Starovoitov [this message]
2017-10-13 19:24 ` Abhijit Ayarekar
2017-10-13 22:10 ` Alexei Starovoitov
2017-10-13 22:12 ` Abhijit Ayarekar
2017-10-14 23:10 ` Daniel Borkmann
2017-10-12 23:45 ` Abhijit Ayarekar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171013011359.tyhynrjghe2krxec@ast-mbp \
--to=alexei.starovoitov@gmail.com \
--cc=abhijit.ayarekar@caviumnetworks.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox