linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Sebastian Reichel <sre@kernel.org>,
	"Gustavo F. Padovan" <gustavo@padovan.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 2/2] Bluetooth: hci_bcm: Add support for BCM2E7E
Date: Thu, 5 Oct 2017 09:46:27 +0200	[thread overview]
Message-ID: <78322c1c-5c71-75b5-00bb-7afa78cf2bbe@redhat.com> (raw)
In-Reply-To: <C0704E2C-0EA2-41B4-A7CB-0E5D0A624C19@holtmann.org>

Hi,

On 04-10-17 21:07, Marcel Holtmann wrote:
> Hi Hans,
> 
>>>> This will happen automatically with this patch series,
>>>> but with the current 4.14 bluetooth stack it will work in
>>>> USB mode, and if we then merge this series post 4.14
>>>> bluetooth will stop working without users doing a btattach
>>>> command from userspace and we will have a regression on
>>>> our hands.
>>> Once the series from Frédéric Danis lands, you can get
>>> serial based broadcom bluetooth without btattach:
>>> https://www.spinics.net/lists/linux-bluetooth/msg71856.html
>>
>> Oh, cool. Thank you for pointing this out to me. I still
>> believe reverting the workaround for the 0000:0000
>> usb-id device is the right thing to do though.
>>
>> I've tested Frédéric Danis' series and it needed quite
>> some work on one of my devices. I've just submitted
>> a 9 patch series to add all the features the platform
>> code paths of hci_bcm.c have and which were missing from
>> the serdev code paths.
> 
> can you send a revert patch with a proper commit message explaining why we are reverting it and then I take it in with your other patch series.

Hmm, I thought I had already send that? But I cannot find it
in the archives, so it looks like I prepared it but never
send it...

I've send it out now, it would be nice to get the revert
into 4.14 so that we don't end up with one kernel release
where we do support the 0000:0000 usb-id.

Regards,

Hans

      reply	other threads:[~2017-10-05  7:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07 20:25 [PATCH 1/2] Bluetooth: btbcm: Add entry for BCM4356A2 UART bluetooth Hans de Goede
2017-09-07 20:25 ` [PATCH 2/2] Bluetooth: hci_bcm: Add support for BCM2E7E Hans de Goede
2017-10-01  9:27   ` Hans de Goede
2017-10-01 10:35     ` Sebastian Reichel
2017-10-02 15:29       ` Hans de Goede
2017-10-04 19:07         ` Marcel Holtmann
2017-10-05  7:46           ` Hans de Goede [this message]

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=78322c1c-5c71-75b5-00bb-7afa78cf2bbe@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=gustavo@padovan.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=sre@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;
as well as URLs for NNTP newsgroup(s).