From: Kalle Valo <kvalo@codeaurora.org>
To: Anilkumar Kolli <akolli@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH] ath11k: fix build issues on disabling ATH11K_DEBUG
Date: Thu, 02 May 2019 17:38:45 +0300 [thread overview]
Message-ID: <87tvecly4q.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <6e9f3d1bb1a3ec7e925d8866dce0cdb1@codeaurora.org> (Anilkumar Kolli's message of "Thu, 02 May 2019 19:42:22 +0530")
Anilkumar Kolli <akolli@codeaurora.org> writes:
> On 2019-05-02 18:55, Kalle Valo wrote:
>> Anilkumar Kolli <akolli@codeaurora.org> writes:
>>
>> Failed to apply:
>>
>> Applying: ath11k: fix build issues on disabling ATH11K_DEBUG
>> fatal: sha1 information is lacking or useless
>> (drivers/net/wireless/ath/ath11k/dp_rx.c).
>> error: could not build fake ancestor
>> Patch failed at 0001 ath11k: fix build issues on disabling ATH11K_DEBUG
>>
>> Please use ath11k-bringup branch as the baseline so that git can use
>> 3-way merge. Otherwise it will be hard to resolve conflicts.
>
> Hi Kalle,
>
> Could you please try in this order,
> 0001-ath11k-move-per-peer-pktlog-entry-to-per-sta-debugfs.patch
> 0001-ath11k-fix-build-issues-on-disabling-ATH11K_DEBUG.patch
If there are dependencies you should put them in the same patchset,
otherwise there's no guarantee of the order they are applied.
But still this fails to apply, please rebase and resend.
Applying: ath11k: fix build issues on disabling ATH11K_DEBUG
fatal: sha1 information is lacking or useless (drivers/net/wireless/ath/ath11k/dp_rx.c).
error: could not build fake ancestor
Patch failed at 0001 ath11k: fix build issues on disabling ATH11K_DEBUG
--
Kalle Valo
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2019-05-02 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 18:50 [PATCH] ath11k: fix build issues on disabling ATH11K_DEBUG Anilkumar Kolli
2019-05-02 13:25 ` Kalle Valo
2019-05-02 14:12 ` Anilkumar Kolli
2019-05-02 14:38 ` Kalle Valo [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=87tvecly4q.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=akolli@codeaurora.org \
--cc=ath11k@lists.infradead.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.