All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Hauke Mehrtens <hauke@hauke-m.de>
Subject: Re: [PATCH V2 1/2] bcma: add empty PCIe hostmode functions if support is disabled
Date: Mon, 26 Jan 2015 09:11:12 +0100	[thread overview]
Message-ID: <CACna6rxHxJNBaQ6coxu_NYw-_NZkC6gnBE_rrXZmdYQT0XSZeg@mail.gmail.com> (raw)
In-Reply-To: <87iofugh9w.fsf@kamboji.qca.qualcomm.com>

On 26 January 2015 at 07:58, Kalle Valo <kvalo@codeaurora.org> wrote:
> Rafał Miłecki <zajec5@gmail.com> writes:
>
>> This allows us to drop some #ifdef magic (mess).
>>
>> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
>> ---
>> V2: Return false in bcma_core_pci_is_in_hostmode
>>     Don't (accidentally) modify bcma_host_soc_register_driver
>
> It would be far more reliable if you resend the whole patchset instead
> of resending invidiviual patches within the set. Otherwise the chances
> are that I apply the wrong version.

Oops. I always take care of removing old versions from patchwork and
using --in-reply-to, I was hoping it's OK.

How would you like whole patches to be re-send? Should I resend them
independently? Or should every patch from the patchset include
In-Reply-To pointing to its previous version?

Is this just an advise for the future, or would you like me to resend
this patchset too?

-- 
Rafał

  reply	other threads:[~2015-01-26  8:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-25 10:11 [PATCH 1/2] bcma: add empty PCIe hostmode functions if support is disabled Rafał Miłecki
2015-01-25 10:11 ` [PATCH 2/2] bcma: add early_init function for PCIe core and move some fix into it Rafał Miłecki
2015-01-25 13:02 ` [PATCH V2 1/2] bcma: add empty PCIe hostmode functions if support is disabled Rafał Miłecki
2015-01-26  6:58   ` Kalle Valo
2015-01-26  8:11     ` Rafał Miłecki [this message]
2015-01-26 12:31       ` Kalle Valo
2015-01-26 16:17         ` Rafał Miłecki

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=CACna6rxHxJNBaQ6coxu_NYw-_NZkC6gnBE_rrXZmdYQT0XSZeg@mail.gmail.com \
    --to=zajec5@gmail.com \
    --cc=hauke@hauke-m.de \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@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.