From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>,
Andrii Nakryiko <andriin@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: linux-next: manual merge of the net-next tree with the kbuild tree
Date: Fri, 16 Aug 2019 22:39:14 +1000 [thread overview]
Message-ID: <20190816223914.1cc64295@canb.auug.org.au> (raw)
In-Reply-To: <20190816160128.36e5cc4e@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 638 bytes --]
Hi all,
On Fri, 16 Aug 2019 16:01:28 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Thu, 15 Aug 2019 22:21:29 -0700 Andrii Nakryiko <andrii.nakryiko@gmail.com> wrote:
> >
> > Thanks, Stephen! Looks good except one minor issue below.
>
> Thanks for checking.
>
> > > vmlinux_link()
> > > {
> > > + info LD ${2}
> >
> > This needs to be ${1}.
>
> At least its only an information message and doesn't affect the build.
> I will fix my resolution for Monday.
I also fixed it up in today's linux-next (just so people aren't
suprised and report it :-)).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-16 12:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 2:41 linux-next: manual merge of the net-next tree with the kbuild tree Stephen Rothwell
2019-08-16 5:21 ` Andrii Nakryiko
2019-08-16 6:01 ` Stephen Rothwell
2019-08-16 12:39 ` Stephen Rothwell [this message]
2019-08-16 18:03 ` Kees Cook
-- strict thread matches above, loose matches on Subject: below --
2021-04-26 0:26 Stephen Rothwell
2017-04-26 1:09 Stephen Rothwell
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=20190816223914.1cc64295@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andrii.nakryiko@gmail.com \
--cc=andriin@fb.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yamada.masahiro@socionext.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).