From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH v2 0/6] ath10k: pci cleanup
Date: Thu, 25 Apr 2013 11:16:42 +0300 [thread overview]
Message-ID: <87y5c7uis5.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <5178E4DF.8080405@tieto.com> (Michal Kazior's message of "Thu, 25 Apr 2013 10:10:07 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> On 25/04/13 09:56, Kalle Valo wrote:
>> Michal Kazior <michal.kazior@tieto.com> writes:
>>
>>>> Applying: ath10k: remove pci probe retrying
>>>> fatal: sha1 information is lacking or useless (drivers/net/wireless/ath/ath10k/pci.c).
>>>> Repository lacks necessary blobs to fall back on 3-way merge.
>>>> Cannot fall back to three-way merge.
>>>> Patch failed at 0003 ath10k: remove pci probe retrying
>>>>
>>>> I didn't want to start manually fixing the conflict, so can you please
>>>> rebase? And please double check how you submit patches, git still
>>>> complains about invalid ids. Of course it might be something on my end,
>>>> but your patches are the only ones with which I have noticed this
>>>> problem.
>>>
>>> I've made sure to send the v2 with no private patches around. When
>>> rebasing I had to resolve the conflict on this patch myself too. It
>>> was in conflict with the hif_type variable removal.
>>>
>>> I use this command:
>>>
>>> git send-email --annotate --cover-letter [--subject-prefix=..]
>>> [--in-reply-to=..] commit_id..commit_id
>>
>> Ok, so you don't use 'git format-patch' at all? I wonder if that makes
>> the difference here. I would assume not.
>>
>>> I also rebase against your github/master branch.
>>
>> What commands do you use to rebase? Have you verified that there are no
>> private commits, eg. merges?
>
> ; git rebase github/master
> (github is my remote name for your github ath10k repository)
>
> If I have some private commits around I do a temporary branch, rebase
> interactively and drop those commits.
> ; git rebase -i github/master
Looks good to me.
> I then do `git send-email` with `github/master..` so I'd probably see
> more patches than I should (after being dropped into editor for
> annotate/cover letter) if there were private commits still around.
Yeah.
This is so weird as with Bartosz' patches I don't have any problems. For
example the last patchset I applied had three patches conflicting and
3-way was always used.
--
Kalle Valo
next prev parent reply other threads:[~2013-04-25 8:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 10:19 [ath9k-devel] [PATCH 0/6] ath10k: pci cleanup Michal Kazior
2013-04-24 10:19 ` [ath9k-devel] [PATCH 1/6] ath10k: fix pci_set_drvpriv ordering Michal Kazior
2013-04-24 10:19 ` [ath9k-devel] [PATCH 2/6] ath10k: refactor pci interrupt functions Michal Kazior
2013-04-24 10:19 ` [ath9k-devel] [PATCH 3/6] ath10k: remove pci probe retrying Michal Kazior
2013-04-24 10:19 ` [ath9k-devel] [PATCH 4/6] ath10k: remove ath10k_pci_configure() Michal Kazior
2013-04-24 10:19 ` [ath9k-devel] [PATCH 5/6] ath10k: remove ath10k_pci_probe_device() Michal Kazior
2013-04-24 10:20 ` [ath9k-devel] [PATCH 6/6] ath10k: simplify pci target reset Michal Kazior
2013-04-24 11:22 ` [ath9k-devel] [PATCH 0/6] ath10k: pci cleanup Michal Kazior
2013-04-24 12:26 ` [ath9k-devel] [PATCH v2 " Michal Kazior
2013-04-24 12:26 ` [ath9k-devel] [PATCH v2 1/6] ath10k: fix pci_set_drvpriv ordering Michal Kazior
2013-04-24 12:26 ` [ath9k-devel] [PATCH v2 2/6] ath10k: refactor pci interrupt functions Michal Kazior
2013-04-24 12:26 ` [ath9k-devel] [PATCH v2 3/6] ath10k: remove pci probe retrying Michal Kazior
2013-04-24 12:26 ` [ath9k-devel] [PATCH v2 4/6] ath10k: remove ath10k_pci_configure() Michal Kazior
2013-04-24 12:26 ` [ath9k-devel] [PATCH v2 5/6] ath10k: remove ath10k_pci_probe_device() Michal Kazior
2013-04-24 12:26 ` [ath9k-devel] [PATCH v2 6/6] ath10k: simplify pci target reset Michal Kazior
2013-04-25 7:24 ` [ath9k-devel] [PATCH v2 0/6] ath10k: pci cleanup Kalle Valo
2013-04-25 7:36 ` Michal Kazior
2013-04-25 7:56 ` Kalle Valo
2013-04-25 7:59 ` Bartosz.Markowski at tieto.com
2013-04-25 8:10 ` Michal Kazior
2013-04-25 8:16 ` Kalle Valo [this message]
2013-04-25 7:24 ` [ath9k-devel] [PATCH v3 " Michal Kazior
2013-04-25 7:24 ` [ath9k-devel] [PATCH v3 1/6] ath10k: fix pci_set_drvpriv ordering Michal Kazior
2013-04-26 6:45 ` Kalle Valo
2013-04-26 6:49 ` Michal Kazior
2013-04-25 7:24 ` [ath9k-devel] [PATCH v3 2/6] ath10k: refactor pci interrupt functions Michal Kazior
2013-04-25 7:24 ` [ath9k-devel] [PATCH v3 3/6] ath10k: remove pci probe retrying Michal Kazior
2013-04-25 7:24 ` [ath9k-devel] [PATCH v3 4/6] ath10k: remove ath10k_pci_configure() Michal Kazior
2013-04-25 7:24 ` [ath9k-devel] [PATCH v3 5/6] ath10k: remove ath10k_pci_probe_device() Michal Kazior
2013-04-25 7:24 ` [ath9k-devel] [PATCH v3 6/6] ath10k: simplify pci target reset Michal Kazior
2013-04-26 6:16 ` [ath9k-devel] [PATCH v3 0/6] ath10k: pci cleanup Kalle Valo
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=87y5c7uis5.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.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.