From: Anh Tuan Phan <tuananhlfc@gmail.com>
To: Stanislav Fomichev <sdf@google.com>
Cc: daniel <daniel@iogearbox.net>,
"martin.lau" <martin.lau@linux.dev>, ast <ast@kernel.org>,
andrii <andrii@kernel.org>, bpf <bpf@vger.kernel.org>,
linux-kernel-mentees
<linux-kernel-mentees@lists.linuxfoundation.org>
Subject: Re: [PATCH v2] samples/bpf: Fix build out of source tree
Date: Sun, 30 Jul 2023 20:19:51 +0700 [thread overview]
Message-ID: <cc5a6736-5fa8-1bae-8649-e113fb32c483@gmail.com> (raw)
In-Reply-To: <CAKH8qBtJ-Nb--BqH+J6K4S++J7J-8uHTPewS3BrVA86GBry=sQ@mail.gmail.com>
On 7/28/23 23:30, Stanislav Fomichev wrote:
> On Thu, Jul 27, 2023 at 5:43 PM Anh Tuan Phan <tuananhlfc@gmail.com> wrote:
>>
>> This commit fixes a few compilation issues when building out of source
>> tree. The command that I used to build samples/bpf:
>>
>> export KBUILD_OUTPUT=/tmp
>> make V=1 M=samples/bpf
>>
>> The compilation failed since it tried to find the header files in the
>> wrong places between output directory and source tree directory
>
> I was going to test it locally, but I can't apply it. Patchwork also
> complains about the same issue:
> stderr: 'error: corrupt patch at line 33
>
> Are you copy-pasting it to gmail maybe? (or manually edited it after
> git format-patch?)
> Maybe rebase, and resend properly with git send-email?
>
It was the copy paste problem. I rebased and sent again by git
send-email. Sorry for the inconvenient.
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
prev parent reply other threads:[~2023-07-30 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 0:43 [PATCH v2] samples/bpf: Fix build out of source tree Anh Tuan Phan
2023-07-28 16:30 ` Stanislav Fomichev via Linux-kernel-mentees
2023-07-30 13:19 ` Anh Tuan Phan [this message]
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=cc5a6736-5fa8-1bae-8649-e113fb32c483@gmail.com \
--to=tuananhlfc@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.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