From: Jeremy Kerr <jk@codeconstruct.com.au>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, kuba@kernel.org,
matt@codeconstruct.com.au, brendanhiggins@google.com,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] mctp: test: disallow MCTP_TEST when building as a module
Date: Sun, 03 Oct 2021 10:22:47 +0800 [thread overview]
Message-ID: <7e6403c499f2483edeb34dccef5cbd27dec4e47d.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20211002.140152.1798934215442988990.davem@davemloft.net>
Hi David,
> Jeremy I had to revert your entire series because of this.
>
> You will need rseubmit the entire series with this build failure
> fixed.
OK, thanks for letting me know, apologies for the breakage. Looks like
my MCTP=m pre-send check didn't end up enabling MCTP_TEST...
v2 coming shortly.
Cheers,
Jeremy
prev parent reply other threads:[~2021-10-03 2:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 2:26 [PATCH net-next 1/2] mctp: test: disallow MCTP_TEST when building as a module Jeremy Kerr
2021-10-02 2:26 ` [PATCH net-next 2/2] mctp: test: defer mdev setup until we've registered Jeremy Kerr
2021-10-02 3:16 ` David Gow
2021-10-03 3:24 ` Jeremy Kerr
2021-10-02 3:10 ` [PATCH net-next 1/2] mctp: test: disallow MCTP_TEST when building as a module David Gow
2021-10-04 2:21 ` Jeremy Kerr
2021-10-06 8:01 ` David Gow
2021-10-11 2:10 ` Jeremy Kerr
2021-10-12 4:38 ` David Gow
2021-10-12 19:38 ` Brendan Higgins
2021-10-12 20:27 ` Daniel Latypov
2021-10-13 19:16 ` Daniel Latypov
2021-10-12 19:52 ` Brendan Higgins
2021-10-21 6:17 ` Jeremy Kerr
2021-10-21 7:06 ` David Gow
2021-10-25 20:54 ` Brendan Higgins
2022-01-06 10:53 ` Jeremy Kerr
2022-01-28 7:41 ` David Gow
2022-01-28 7:54 ` David Gow
2021-10-02 13:01 ` David Miller
2021-10-03 2:22 ` Jeremy Kerr [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=7e6403c499f2483edeb34dccef5cbd27dec4e47d.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=brendanhiggins@google.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
/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).