linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org,
	Yan-Hsuan Chuang <yhchuang@realtek.com>,
	Ping-Ke Shih <pkshih@realtek.com>,
	Birming Chiu <birming@realtek.com>, Shaofu <shaofu@realtek.com>,
	Steven Ting <steventing@realtek.com>
Subject: Re: [PATCH 2/9] rtlwifi: btcoex: rename ex_halbtc....YZant to ex_btc.....YZant
Date: Mon, 05 Jun 2017 18:13:45 +0300	[thread overview]
Message-ID: <87vaoa79hy.fsf@qca.qualcomm.com> (raw)
In-Reply-To: 87bmq28p6l.fsf@codeaurora.org

(Removing the X letters from the subject to bypass vger filters)

Kalle Valo <kvalo@codeaurora.org> writes:

> Larry Finger <Larry.Finger@lwfinger.net> writes:
>
>> From: Yan-Hsuan Chuang <yhchuang@realtek.com>
>>
>> These external functions are for BT-coexistence, so remove the "hal"
>> prefix for consistancy.
>>
>> Signed-off-by: Yan-Hsuan Chuang <yhchuang@realtek.com>
>> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
>> Cc: Ping-Ke Shih <pkshih@realtek.com>
>> Cc: Birming Chiu <birming@realtek.com>
>> Cc: Shaofu <shaofu@realtek.com>
>> Cc: Steven Ting <steventing@realtek.com>
>
> On my inbox I see four different versions of this patch 2 but on
> patchwork I only see one, but with a different date than rest of the
> patches in this series and hence is wrong order. What happened, did you
> perhaps delete some of the patches from patchwork?
>
> But anyway, if there are accidental multiple patch submissions please
> always submit the whole series again as v2. Resubmitting is the most
> reliable method to make sure that I apply the correct version of
> patches, anything is else is just confusing me and increases the chances
> that I apply the wrong version.

Hehe, so I think I now understand what happened:

<linux-wireless@vger.kernel.org>: host vger.kernel.org[209.132.180.67] said:
    550 5.7.1 Content-Policy reject msg: The capital Triple-X in subject is way
    too often associated with junk email, please rephrase.  BF:<H 0>;
    S1751112AbdFEOtn (in reply to end of DATA command)

But anyway, please resubmit the whole series as v2.

-- 
Kalle Valo

           reply	other threads:[~2017-06-05 15:13 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <87bmq28p6l.fsf@codeaurora.org>]

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=87vaoa79hy.fsf@qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=birming@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=shaofu@realtek.com \
    --cc=steventing@realtek.com \
    --cc=yhchuang@realtek.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).