[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABBYNZKpYuW6+iZJomaykGLT6gF2NBjTxjw-27vBZRY89P3xgw@mail.gmail.com>
Date: Sun, 9 Jan 2022 19:57:20 -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 6:56 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Sun, 9 Jan 2022 18:46:05 -0800 Luiz Augusto von Dentz wrote:
> > > You're right. I think our patchwork build bot got confused about the
> > > direction of the merge and displayed old warnings :S You know what..
> > > let me just pull this as is and we can take the fixes in the next PR,
> > > then. Apologies for the extra work!
> >
> > 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? Or you actually pulled the head of bluetooth-next not tag?
--
Luiz Augusto von Dentz
Powered by blists - more mailing lists