LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Dmitry Tunin <hanipouspilot@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>,
	linux-bluetooth <linux-bluetooth@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [REGRESSION] And a drity fix for 0cf3:3004 QCA Rome device
Date: Sun, 13 May 2018 16:08:07 +0300	[thread overview]
Message-ID: <CANoib0FoY86caY-zABHssXq_G8zmt3zJemvYrTyvQ1R58xseoQ@mail.gmail.com> (raw)

Hi, Marcel

Since  f44cb4b older AR3012 devices stopped working. We discussed that
before that QCA released a ROME device with a duplicate code.

If there is no easy way to check which one is used, then it may be a
good decision to change the kernel code for the newer device in new
kernels.

But anyway it should be made cleaner. The device is still listed in
ath3k.o as an AR3012.

Regards,

Dmitry.

             reply	other threads:[~2018-05-13 13:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-13 13:08 Dmitry Tunin [this message]
2018-05-13 13:20 ` Dmitry Tunin

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=CANoib0FoY86caY-zABHssXq_G8zmt3zJemvYrTyvQ1R58xseoQ@mail.gmail.com \
    --to=hanipouspilot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --subject='Re: [REGRESSION] And a drity fix for 0cf3:3004 QCA Rome device' \
    /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

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).