linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: miaoqinglang <miaoqinglang@huawei.com>
Cc: Jakub Kicinski <kubakici@wp.pl>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	<linux-wireless@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] mt7601u: Convert to DEFINE_SHOW_ATTRIBUTE
Date: Fri, 09 Oct 2020 18:45:09 +0300	[thread overview]
Message-ID: <87a6wvs8sa.fsf@tynnyri.adurom.net> (raw)
In-Reply-To: <87eem7s8wi.fsf@tynnyri.adurom.net> (Kalle Valo's message of "Fri, 09 Oct 2020 18:42:37 +0300")

Kalle Valo <kvalo@codeaurora.org> writes:

> miaoqinglang <miaoqinglang@huawei.com> writes:
>
>> 在 2020/7/16 23:20, Jakub Kicinski 写道:
>>> On Thu, 16 Jul 2020 16:57:49 +0800 Qinglang Miao wrote:
>>>> Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
>>>>
>>>> Signed-off-by: Qinglang Miao <miaoqinglang@huawei.com>
>>>
>>> Acked-by: Jakub Kicinski <kubakici@wp.pl>
>>>
>> Hi Jakub,
>>
>> I noticed that this patch has been acked by you and not patched into
>> linux-next. There's little difference now so resent a new patch
>> against linux-next(20200917), and it can be applied to mainline
>> cleanly now.
>
> This patch didn't apply to wireless-drivers-next and my script sent you
> an email about it:
>
> https://patchwork.kernel.org/patch/11666949/
>
> Please rebase over latest wireless-drivers-next and resend as v2.

Nevermind, I see that you sent v2 already and that was applied. Sorry
for the noise.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2020-10-09 15:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16  8:57 [PATCH -next] mt7601u: Convert to DEFINE_SHOW_ATTRIBUTE Qinglang Miao
2020-07-16 15:20 ` Jakub Kicinski
2020-09-19  2:49   ` miaoqinglang
2020-10-09 15:42     ` Kalle Valo
2020-10-09 15:45       ` Kalle Valo [this message]
2020-08-02 15:11 ` 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=87a6wvs8sa.fsf@tynnyri.adurom.net \
    --to=kvalo@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kubakici@wp.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=miaoqinglang@huawei.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).