From: Dmitry Tunin <hanipouspilot@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] ath3k: Add support of AR3012 bluetooth 13d3:3423 device
Date: Sat, 17 Jan 2015 22:57:05 +0300 [thread overview]
Message-ID: <54BABE91.8020609@gmail.com> (raw)
In-Reply-To: <F80A6947-61FA-46A1-8742-51129F4E18C3@holtmann.org>
Any ideas what may be wrong? Is the tree URL correct or there is another bluetooth-next branch I dot know about?
I just clean cloned it again and applied with no problem.
17.01.2015 21:59, Marcel Holtmann пишет:
> Hi Dmitry,
>
> please do not top post on this mailing list.
>
>> This patch is against git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git
>> Or is it another branch?
>>
>> I pulled it again, but still no changes. Why it can be?
>
> it neither applies with git am, nor manually running patch.
>
> checking file drivers/bluetooth/ath3k.c
> Hunk #1 FAILED at 108.
> Hunk #2 FAILED at 162.
> 2 out of 2 hunks FAILED
> checking file drivers/bluetooth/btusb.c
> Hunk #1 FAILED at 189.
> 1 out of 1 hunk FAILED
>
> Regards
>
> Marcel
>
next prev parent reply other threads:[~2015-01-17 19:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 21:45 [PATCH] ath3k: Add support of AR3012 bluetooth 13d3:3423 device Dmitry Tunin
2015-01-17 4:32 ` Marcel Holtmann
2015-01-17 8:26 ` Dmitry Tunin
2015-01-17 18:59 ` Marcel Holtmann
2015-01-17 19:57 ` Dmitry Tunin [this message]
2015-01-17 20:05 ` Marcel Holtmann
2015-01-17 16:40 ` Dmitry Tunin
2015-01-17 21:01 ` Dmitry Tunin
2015-01-18 10:57 ` Dmitry Tunin
-- strict thread matches above, loose matches on Subject: below --
2015-01-17 21:15 Dmitry Tunin
2015-01-17 22:03 ` 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=54BABE91.8020609@gmail.com \
--to=hanipouspilot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.