From: Gal Pressman <galpress@amazon.com>
To: kernel test robot <lkp@intel.com>, Jason Gunthorpe <jgg@ziepe.ca>,
"Doug Ledford" <dledford@redhat.com>
Cc: <kbuild-all@lists.01.org>, <clang-built-linux@googlegroups.com>,
<linux-rdma@vger.kernel.org>,
Alexander Matushevsky <matua@amazon.com>,
"Shadi Ammouri" <sammouri@amazon.com>,
Yossi Leybovich <sleybo@amazon.com>
Subject: Re: [PATCH for-next v2 3/4] RDMA/efa: User/kernel compatibility handshake mechanism
Date: Tue, 21 Jul 2020 14:26:55 +0300 [thread overview]
Message-ID: <99314564-cb73-5a25-3583-1afda323d2b3@amazon.com> (raw)
In-Reply-To: <202007210118.fF0Xv5Jy%lkp@intel.com>
On 20/07/2020 20:08, kernel test robot wrote:
> Hi Gal,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on 5f0b2a6093a4d9aab093964c65083fe801ef1e58]
>
> url: https://github.com/0day-ci/linux/commits/Gal-Pressman/Add-support-for-0xefa1-device/20200720-160419
> base: 5f0b2a6093a4d9aab093964c65083fe801ef1e58
> config: x86_64-allyesconfig (attached as .config)
> compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project cf1105069648446d58adfb7a6cc590013d6886ba)
Uh, looks like I use some gcc specific stuff here.. I guess it's time to start
checking clang compilation as well :).
Will fix and resubmit.
next prev parent reply other threads:[~2020-07-21 11:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 8:01 [PATCH for-next v2 0/4] Add support for 0xefa1 device Gal Pressman
2020-07-20 8:01 ` [PATCH for-next v2 1/4] RDMA/efa: Expose maximum TX doorbell batch Gal Pressman
2020-07-20 8:01 ` [PATCH for-next v2 2/4] RDMA/efa: Expose minimum SQ size Gal Pressman
2020-07-20 8:01 ` [PATCH for-next v2 3/4] RDMA/efa: User/kernel compatibility handshake mechanism Gal Pressman
2020-07-20 17:08 ` kernel test robot
2020-07-21 11:26 ` Gal Pressman [this message]
2020-07-21 17:10 ` Nick Desaulniers
2020-07-22 6:35 ` Gal Pressman
2020-07-22 15:51 ` Nathan Chancellor
2020-07-20 8:01 ` [PATCH for-next v2 4/4] RDMA/efa: Add EFA 0xefa1 PCI ID Gal Pressman
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=99314564-cb73-5a25-3583-1afda323d2b3@amazon.com \
--to=galpress@amazon.com \
--cc=clang-built-linux@googlegroups.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kbuild-all@lists.01.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lkp@intel.com \
--cc=matua@amazon.com \
--cc=sammouri@amazon.com \
--cc=sleybo@amazon.com \
/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;
as well as URLs for NNTP newsgroup(s).