From: Sedat Dilek <sedat.dilek@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Yonghong Song <yhs@fb.com>, Andrii Nakryiko <andrii@kernel.org>,
Jiri Olsa <jolsa@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <natechancellor@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Clang-Built-Linux ML <clang-built-linux@googlegroups.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
Jakub Jelinek <jakub@redhat.com>,
Fangrui Song <maskray@google.com>,
Caroline Tice <cmtice@google.com>,
Nick Clifton <nickc@redhat.com>,
dwarves@vger.kernel.org, bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH v5 0/3] Kbuild: DWARF v5 support
Date: Thu, 4 Feb 2021 09:42:13 +0100 [thread overview]
Message-ID: <CA+icZUW2omV581KN0Qv=nGsk=6a-GG2Cm2OYeRxETrZP_obwEQ@mail.gmail.com> (raw)
In-Reply-To: <CAEf4Bzbn1app3LZ1oah5ARn81j5RMNxRRHPVAkeY3h_0q7+7fg@mail.gmail.com>
On Thu, Feb 4, 2021 at 3:58 AM Andrii Nakryiko
<andrii.nakryiko@gmail.com> wrote:
...
>
> Is there another (easy) way to get your patch set without the b4 tool?
> Is your patch set present in some patchworks instance, so that I can
> download it in mbox format, for example?
>
Just to promote the b4 tool - we have some cool wiki in [1].
Personally, I got in touch with b4 when dealing with the
ClangBuiltLinux project.
Note: Sometimes it takes a bit for the patch(set) to be available from
the LORE link.
- Sedat -
[1] https://github.com/ClangBuiltLinux/linux/wiki/Command-line-tips-and-tricks#fetching-a-single-patch-or-series-from-lkml
next prev parent reply other threads:[~2021-02-04 8:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210115210616.404156-1-ndesaulniers@google.com>
[not found] ` <CA+icZUVp+JNq89uc_DyWC6zh5=kLtUr7eOxHizfFggnEVGJpqw@mail.gmail.com>
[not found] ` <7354583d-de40-b6b9-6534-a4f4c038230f@fb.com>
[not found] ` <CAKwvOd=5iR0JONwDb6ypD7dzzjOS3Uj0CjcyYqPF48eK4Pi90Q@mail.gmail.com>
[not found] ` <12b6c2ca-4cf7-4edd-faf2-72e3cb59c00e@fb.com>
[not found] ` <20210117201500.GO457607@kernel.org>
2021-02-04 1:31 ` [PATCH v5 0/3] Kbuild: DWARF v5 support Nick Desaulniers
2021-02-04 2:57 ` Andrii Nakryiko
2021-02-04 3:13 ` Nick Desaulniers
2021-02-04 23:54 ` Andrii Nakryiko
2021-02-05 0:04 ` Nick Desaulniers
2021-02-05 0:06 ` Andrii Nakryiko
2021-02-05 0:11 ` Nick Desaulniers
2021-02-05 0:17 ` Andrii Nakryiko
2021-02-04 8:42 ` Sedat Dilek [this message]
2021-02-04 8:59 ` Sedat Dilek
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='CA+icZUW2omV581KN0Qv=nGsk=6a-GG2Cm2OYeRxETrZP_obwEQ@mail.gmail.com' \
--to=sedat.dilek@gmail.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=cmtice@google.com \
--cc=dwarves@vger.kernel.org \
--cc=jakub@redhat.com \
--cc=jolsa@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=maskray@google.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=nickc@redhat.com \
--cc=yhs@fb.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).