From: David Miller <davem@davemloft.net>
To: masahiroy@kernel.org
Cc: jon.maloy@ericsson.com, ying.xue@windriver.com,
netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] tipc: remove meaningless assignment in Makefile
Date: Wed, 08 Jan 2020 12:39:13 -0800 (PST) [thread overview]
Message-ID: <20200108.123913.1956180963816835480.davem@davemloft.net> (raw)
In-Reply-To: <20200106073527.18697-2-masahiroy@kernel.org>
From: Masahiro Yamada <masahiroy@kernel.org>
Date: Mon, 6 Jan 2020 16:35:27 +0900
> There is no module named tipc_diag.
>
> The assignment to tipc_diag-y has no effect.
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Applied.
next prev parent reply other threads:[~2020-01-08 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 7:35 [PATCH 1/2] tipc: do not add socket.o to tipc-y twice Masahiro Yamada
2020-01-06 7:35 ` [PATCH 2/2] tipc: remove meaningless assignment in Makefile Masahiro Yamada
2020-01-08 20:39 ` David Miller [this message]
2020-01-08 20:39 ` [PATCH 1/2] tipc: do not add socket.o to tipc-y twice David Miller
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=20200108.123913.1956180963816835480.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.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).