From: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org,
Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>,
Avinash Patil <avinashp@quantenna.com>,
Vasily Ulyanov <vulyanov@quantenna.com>
Subject: Re: [1/5] qtnfmac: modify full Tx queue error reporting
Date: Sun, 29 Oct 2017 18:32:12 +0300 [thread overview]
Message-ID: <20171029153211.4ynfo6wrh7q76efd@bars> (raw)
In-Reply-To: <20171027084814.B3FCB60314@smtp.codeaurora.org>
Hello Kalle,
> Failed to apply:
>
> fatal: sha1 information is lacking or useless (drivers/net/wireless/quantenna/qtnfmac/pearl/pcie.c).
> error: could not build fake ancestor
> Applying: qtnfmac: modify full Tx queue recovery
> Patch failed at 0001 qtnfmac: modify full Tx queue recovery
> The copy of the patch that failed is found in: .git/rebase-apply/patch
>
> 5 patches set to Changes Requested.
>
> 10007281 [1/5] qtnfmac: modify full Tx queue error reporting
> 10007279 [2/5] qtnfmac: enable registration of more mgmt frames
> 10007283 [3/5] qtnfmac: drop nonexistent function declaration
> 10007285 [4/5] qtnfmac: modify full Tx queue recovery
> 10007287 [5/5] qtnfmac: advertise support of inactivity timeout
My assumption is that by default all the patches should cleanly apply to wireless-drivers-next.
I could apply the patch in question to wireless-drivers-next without any issues.
Rebase of the whole series on top of wireless-drivers-next looks good as well.
I will resend rebased patches as v2. Meanwhile do you have any idea what could go wrong ?
The error message looks scary...
Regards,
Sergey
next prev parent reply other threads:[~2017-10-29 15:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 20:53 [PATCH 0/8] qtnfmac: misc small features and fixes Sergey Matyukevich
2017-10-15 20:53 ` [PATCH 1/5] qtnfmac: modify full Tx queue error reporting Sergey Matyukevich
2017-10-27 8:48 ` [1/5] " Kalle Valo
2017-10-29 15:32 ` Sergey Matyukevich [this message]
2017-10-30 8:02 ` Kalle Valo
2017-10-30 9:45 ` Sergey Matyukevich
2017-10-30 10:31 ` Kalle Valo
2017-10-15 20:53 ` [PATCH 2/5] qtnfmac: enable registration of more mgmt frames Sergey Matyukevich
2017-10-15 20:53 ` [PATCH 3/5] qtnfmac: drop nonexistent function declaration Sergey Matyukevich
2017-10-15 20:53 ` [PATCH 4/5] qtnfmac: modify full Tx queue recovery Sergey Matyukevich
2017-10-15 20:53 ` [PATCH 5/5] qtnfmac: advertise support of inactivity timeout Sergey Matyukevich
2017-10-16 19:22 ` [PATCH 0/8] qtnfmac: misc small features and fixes Igor Mitsyanko
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=20171029153211.4ynfo6wrh7q76efd@bars \
--to=sergey.matyukevich.os@quantenna.com \
--cc=avinashp@quantenna.com \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=vulyanov@quantenna.com \
/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).