From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: patchwork-bot+netdevbpf@kernel.org, davem@davemloft.net,
kuba@kernel.org, linux-bluetooth@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: pull request: bluetooth 2024-07-26
Date: Sat, 10 Aug 2024 04:54:44 +0900 [thread overview]
Message-ID: <ZrZ0BHp5-eHGcaV-@zx2c4.com> (raw)
In-Reply-To: <CABBYNZJW7t=yDbZi68L_g3iwTWatGDk=WAfv1acQWY_oG-_QPA@mail.gmail.com>
Hi,
On Fri, Aug 09, 2024 at 11:12:32AM -0400, Luiz Augusto von Dentz wrote:
> Hi,
>
> On Fri, Aug 9, 2024 at 10:48 AM Luiz Augusto von Dentz
> <luiz.dentz@gmail.com> wrote:
> >
> > Hi Jakub,
> >
> > On Wed, Aug 7, 2024 at 11:40 PM <patchwork-bot+netdevbpf@kernel.org> wrote:
> > >
> > > Hello:
> > >
> > > This pull request was applied to netdev/net.git (main)
> > > by Jakub Kicinski <kuba@kernel.org>:
> > >
> > > On Wed, 7 Aug 2024 17:01:03 -0400 you wrote:
> > > > The following changes since commit 1ca645a2f74a4290527ae27130c8611391b07dbf:
> > > >
> > > > net: usb: qmi_wwan: add MeiG Smart SRM825L (2024-08-06 19:35:08 -0700)
> > > >
> > > > are available in the Git repository at:
> > > >
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git tags/for-net-2024-08-07
> > > >
> > > > [...]
> > >
> > > Here is the summary with links:
> > > - pull request: bluetooth 2024-07-26
> > > https://git.kernel.org/netdev/net/c/b928e7d19dfd
> > >
> > > You are awesome, thank you!
> >
> > Im trying to rebase on top of net-next but Im getting the following error:
> >
> > In file included from arch/x86/entry/vdso/vgetrandom.c:7:
> > arch/x86/entry/vdso/../../../../lib/vdso/getrandom.c: In function
> > ‘memcpy_and_zero_src’:
> > arch/x86/entry/vdso/../../../../lib/vdso/getrandom.c:18:17: error:
> > implicit declaration of function ‘__put_unaligned_t’; did you mean
> > ‘__put_unaligned_le24’? [-Wimplicit-function-declaration]
> >
> > I tried to google it but got no results, perhaps there is something
> > wrong with my .config, it used to work just fine but it seems
> > something had changed.
>
> Looks like the culprit is "x86: vdso: Wire up getrandom() vDSO
> implementation", if I revert that I got it to build properly.
>
> @Jason A. Donenfeld since you are the author of the specific change
> perhaps you can tell me what is going on, my .config is based on:
>
> https://github.com/Vudentz/BlueZ/blob/master/doc/test-runner.txt
Could you send your actual .config so I can repro?
Thanks,
Jason
next prev parent reply other threads:[~2024-08-09 19:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 21:01 pull request: bluetooth 2024-07-26 Luiz Augusto von Dentz
2024-08-08 3:40 ` patchwork-bot+netdevbpf
2024-08-09 14:48 ` Luiz Augusto von Dentz
2024-08-09 15:12 ` Luiz Augusto von Dentz
2024-08-09 19:54 ` Jason A. Donenfeld [this message]
2024-08-09 20:02 ` Luiz Augusto von Dentz
2024-08-09 20:21 ` Jason A. Donenfeld
2024-08-15 16:32 ` Luiz Augusto von Dentz
2024-08-15 16:38 ` Luiz Augusto von Dentz
2024-08-15 17:47 ` patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2024-07-26 15:05 Luiz Augusto von Dentz
2024-07-27 1:40 ` patchwork-bot+netdevbpf
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=ZrZ0BHp5-eHGcaV-@zx2c4.com \
--to=jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=patchwork-bot+netdevbpf@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