From: Jakub Kicinski <kuba@kernel.org>
To: "Von Dentz, Luiz" <luiz.von.dentz@intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Networking <netdev@vger.kernel.org>,
"Alexander Mikhalitsyn" <alexander@mihalicyn.com>,
Kuniyuki Iwashima <kuniyu@amazon.com>
Subject: Re: linux-next: build failure after merge of the bluetooth tree
Date: Wed, 19 Jul 2023 20:24:35 -0700 [thread overview]
Message-ID: <20230719202435.636dcc3a@kernel.org> (raw)
In-Reply-To: <PH0PR11MB5126763E5913574B8ED6BDE4D33EA@PH0PR11MB5126.namprd11.prod.outlook.com>
On Thu, 20 Jul 2023 03:17:37 +0000 Von Dentz, Luiz wrote:
> Sorry for not replying inline, outlook on android, we use scm_recv
> not scm_recv_unix, so Id assume that change would return the initial
> behavior, if it did not then it is not fixing anything.
Ack, that's what it seems like to me as well.
I fired up an allmodconfig build of linux-next. I should be able
to get to the bottom of this in ~20min :)
next prev parent reply other threads:[~2023-07-20 3:24 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PH0PR11MB51269B6805230AB8ED209B14D332A@PH0PR11MB5126.namprd11.prod.outlook.com>
2023-07-20 0:50 ` linux-next: build failure after merge of the bluetooth tree Stephen Rothwell
2023-07-20 1:24 ` Jakub Kicinski
2023-07-20 3:00 ` Stephen Rothwell
[not found] ` <PH0PR11MB5126763E5913574B8ED6BDE4D33EA@PH0PR11MB5126.namprd11.prod.outlook.com>
2023-07-20 3:24 ` Jakub Kicinski [this message]
2023-07-20 6:00 ` Alexander Mikhalitsyn
2023-07-20 15:14 ` Jakub Kicinski
2023-07-20 15:21 ` Alexander Mikhalitsyn
2023-07-20 22:19 ` Stephen Rothwell
2023-07-20 22:12 ` Stephen Rothwell
2023-07-20 23:27 ` Jakub Kicinski
2023-07-20 23:30 ` Stephen Rothwell
2025-12-18 10:59 Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-07-15 3:09 Stephen Rothwell
2025-07-15 4:36 ` Christian Eggers
2025-01-10 0:57 Stephen Rothwell
2024-08-30 1:42 Stephen Rothwell
2024-05-01 1:19 Stephen Rothwell
2024-05-01 1:34 ` Sungwoo Kim
2023-07-20 22:21 Iwashima, Kuniyuki
[not found] <PH0PR11MB51262F07CD4739BDCB920483D322A@PH0PR11MB5126.namprd11.prod.outlook.com>
2023-06-23 8:34 ` Alexander Mikhalitsyn
2023-06-23 9:23 ` Alexander Mikhalitsyn
2023-06-23 12:24 ` Christian Brauner
2023-06-23 12:28 ` Alexander Mikhalitsyn
2023-06-23 15:09 ` Jakub Kicinski
2023-06-26 22:09 ` Alexander Mikhalitsyn
[not found] <PH0PR11MB5126F2B2E020774AF8D91299D35BA@PH0PR11MB5126.namprd11.prod.outlook.com>
2023-06-15 23:27 ` Stephen Rothwell
2023-06-13 3:02 Stephen Rothwell
2023-06-15 22:32 ` Stephen Rothwell
2023-07-06 23:41 ` Stephen Rothwell
2021-12-07 0:26 Stephen Rothwell
2021-12-06 0:37 Stephen Rothwell
2021-09-27 0:16 Stephen Rothwell
[not found] <PH0PR11MB5126EFEDB65650EFC3368981D3749@PH0PR11MB5126.namprd11.prod.outlook.com>
2021-04-08 4:57 ` Stephen Rothwell
2021-04-08 3:59 Stephen Rothwell
2020-07-27 3:44 Stephen Rothwell
2020-07-27 5:22 ` Christoph Hellwig
2020-07-27 13:28 ` Alain Michaud
2019-10-18 0:13 Stephen Rothwell
2015-09-14 0:14 Stephen Rothwell
2015-09-14 0:22 ` Stephen Rothwell
2015-09-22 1:20 ` Stephen Rothwell
2015-09-22 1:20 ` Stephen Rothwell
2015-09-22 3:42 ` David Miller
2015-08-12 8:01 Stephen Rothwell
2014-10-27 2:19 Stephen Rothwell
2014-10-28 14:49 ` Johan Hedberg
2012-09-19 1:45 Stephen Rothwell
2012-02-22 1:21 Stephen Rothwell
2012-02-22 1:29 ` David Miller
2011-12-21 2:19 Stephen Rothwell
2011-04-28 1:41 Stephen Rothwell
2011-04-28 4:12 ` Gustavo F. Padovan
2011-02-15 2:16 Stephen Rothwell
2011-02-15 12:48 ` Gustavo F. Padovan
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=20230719202435.636dcc3a@kernel.org \
--to=kuba@kernel.org \
--cc=alexander@mihalicyn.com \
--cc=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.