From: Waqar Hameed <waqar.hameed@axis.com>
To: Anton Ivanov <anton.ivanov@cambridgegreys.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Ingo Molnar <mingo@kernel.org>, <oe-kbuild-all@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, <kernel@axis.com>,
Richard Weinberger <richard@nod.at>,
<linux-um@lists.infradead.org>
Subject: Re: pcap-dbus.o:undefined reference to `dbus_message_demarshal'
Date: Thu, 7 Mar 2024 12:31:58 +0100 [thread overview]
Message-ID: <pndle6ui8gh.fsf@axis.com> (raw)
In-Reply-To: <4ee83195-99f5-4823-b4d0-339ef4127013@cambridgegreys.com> (Anton Ivanov's message of "Thu, 7 Mar 2024 10:49:56 +0000")
On Thu, Mar 07, 2024 at 10:49 +0000 Anton Ivanov <anton.ivanov@cambridgegreys.com> wrote:
> On 07/03/2024 10:29, Johannes Berg wrote:
[...]
>> Yeah, that makes sense, this is all kind of special configuration
>> anyway, and given that it's been broken forever ...
>> I actually doubt anyone would scream if we just removed it, so maybe
>> just remove it and if they do scream, point to the above, including said
>> 3-liner in the response?
>
> Let's make it so.
I'm guessing Johannes (or Anton) will create the patch for removing it
and no further action is needed from my side.
Thank you for your swift responses!
next prev parent reply other threads:[~2024-03-07 11:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 15:11 pcap-dbus.o:undefined reference to `dbus_message_demarshal' kernel test robot
2024-03-06 16:14 ` Waqar Hameed
2024-03-07 9:54 ` Anton Ivanov
2024-03-07 10:03 ` Johannes Berg
2024-03-07 10:27 ` Anton Ivanov
2024-03-07 10:29 ` Johannes Berg
2024-03-07 10:49 ` Anton Ivanov
2024-03-07 11:31 ` Waqar Hameed [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-26 10:13 kernel test robot
2024-02-14 5:02 kernel test robot
2024-01-07 18:07 kernel test robot
2023-10-10 0:52 kernel test robot
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=pndle6ui8gh.fsf@axis.com \
--to=waqar.hameed@axis.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=johannes@sipsolutions.net \
--cc=kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=mingo@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=richard@nod.at \
/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.