[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CABBYNZLyfoMep6d6oo=x7L+0sOrhyHvgtEh-b7WY9q__aUQ3Lg@mail.gmail.com>
Date: Sun, 9 Jan 2022 22:07:45 -0800
From: Luiz Augusto von Dentz <luiz.dentz@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Marcel Holtmann <marcel@...tmann.org>,
"David S. Miller" <davem@...emloft.net>,
linux-bluetooth <linux-bluetooth@...r.kernel.org>,
"open list:NETWORKING [GENERAL]" <netdev@...r.kernel.org>,
Tedd Ho-Jeong An <hj.tedd.an@...il.com>
Subject: Re: pull request: bluetooth 2022-01-07
Hi Jakub,
On Sun, Jan 9, 2022 at 9:53 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Sun, 9 Jan 2022 19:57:20 -0800 Luiz Augusto von Dentz wrote:
> > On Sun, Jan 9, 2022 at 6:56 PM Jakub Kicinski <kuba@...nel.org> wrote:
> > > > Im planning to send a new pull request later today, that should
> > > > address the warning and also takes cares of sort hash since that has
> > > > been fixup in place.
> > >
> > > But I already pulled..
> >
> > Nevermind then, shall I send the warning fix directly to net-next
> > then?
>
> Maybe send it in a week or so with other fixes which accumulate
> up to that point?
>
> > Or you actually pulled the head of bluetooth-next not tag?
>
> I pulled the tag.
Fair enough, if you would like to merge the warning fix here is the commit:
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=219de95995fb6526b96687c5001f61fe41bed41e
--
Luiz Augusto von Dentz
Powered by blists - more mailing lists