[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220109215302.2d8367c5@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
Date: Sun, 9 Jan 2022 21:53:02 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Luiz Augusto von Dentz <luiz.dentz@...il.com>
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
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.
Powered by blists - more mailing lists