public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel•org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail•com>
Cc: davem@davemloft•net, linux-bluetooth@vger•kernel.org,
	netdev@vger•kernel.org
Subject: Re: pull request: bluetooth 2022-09-09
Date: Mon, 19 Sep 2022 18:04:19 -0700	[thread overview]
Message-ID: <20220919180419.0caa435a@kernel.org> (raw)
In-Reply-To: <CABBYNZKHUbqYyevHRZ=6rLA0GAE20mLRHAj9JnFNuRn7VHrEeA@mail.gmail.com>

On Tue, 13 Sep 2022 16:35:01 -0700 Luiz Augusto von Dentz wrote:
> On Fri, Sep 9, 2022 at 1:16 PM Luiz Augusto von Dentz wrote:
> >
> > The following changes since commit 64ae13ed478428135cddc2f1113dff162d8112d4:
> >
> >   net: core: fix flow symmetric hash (2022-09-09 12:48:00 +0100)
> >
> > are available in the Git repository at:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git tags/for-net-2022-09-09
> >
> > for you to fetch changes up to 35e60f1aadf6c02d77fdf42180fbf205aec7e8fc:
> >
> >   Bluetooth: Fix HCIGETDEVINFO regression (2022-09-09 12:25:18 -0700)
> >
> > ----------------------------------------------------------------
> > bluetooth pull request for net:
> >
> >  -Fix HCIGETDEVINFO regression
> 
> Looks like this still hasn't been applied, is there any problem that
> needs to be fixed?

Sorry about the delay, we were all traveling to Linux Plumbers.
Pulling now.

Any reason why struct hci_dev_info is not under include/uapi ?

  reply	other threads:[~2022-09-20  1:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 20:16 pull request: bluetooth 2022-09-09 Luiz Augusto von Dentz
2022-09-13 23:35 ` Luiz Augusto von Dentz
2022-09-20  1:04   ` Jakub Kicinski [this message]
2022-09-20 20:56     ` Luiz Augusto von Dentz
2022-09-20 21:03       ` Jakub Kicinski
2022-09-20  1:10 ` 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=20220919180419.0caa435a@kernel.org \
    --to=kuba@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=linux-bluetooth@vger$(echo .)kernel.org \
    --cc=luiz.dentz@gmail$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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