linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Lee <tiny.windzz@gmail.com>
To: kvalo@codeaurora.org
Cc: merez@codeaurora.org, davem@davemloft.net,
	linux-wireless@vger.kernel.org, wil6210@qti.qualcomm.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wireless/wil6210: convert to DEFINE_SHOW_ATTRIBUTE
Date: Tue, 11 Dec 2018 23:51:10 +0800	[thread overview]
Message-ID: <CAEExFWuubkuEE57+DPVbwFTw9st6Re72dqtg-JHwQJsxkVF_UA@mail.gmail.com> (raw)
In-Reply-To: <87ftv412wb.fsf@kamboji.qca.qualcomm.com>

On Tue, Dec 11, 2018 at 11:47 PM Kalle Valo <kvalo@codeaurora.org> wrote:
>
> Frank Lee <tiny.windzz@gmail.com> writes:
>
> > On Mon, Dec 3, 2018 at 9:36 PM Frank Lee <tiny.windzz@gmail.com> wrote:
> >>
> >> On Mon, Dec 3, 2018 at 9:33 PM Kalle Valo <kvalo@codeaurora.org> wrote:
> >> >
> >> > Yangtao Li <tiny.windzz@gmail.com> writes:
> >> >
> >> > > Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
> >> > >
> >> > > Signed-off-by: Yangtao Li <tiny.windzz@gmail.com>
> >> >
> >> > The prefix for the title should be just "wil6210:", I can fix that.
> > Hi Kalle:
> > Why I can't find it in ath.git?
>
> Because I haven't reviewed and applied it yet. BTW, you can reduce email
> by checking the status from patchwork yourself:
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#checking_state_of_patches_from_patchwork
Thanks.I hope my email didn't bother you.

MBR,
Yangtao
>
> --
> Kalle Valo

  reply	other threads:[~2018-12-11 16:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 13:25 [PATCH] wireless/wil6210: convert to DEFINE_SHOW_ATTRIBUTE Yangtao Li
2018-12-03 13:33 ` Kalle Valo
2018-12-03 13:36   ` Frank Lee
2018-12-11 15:28     ` Frank Lee
2018-12-11 15:47       ` Kalle Valo
2018-12-11 15:51         ` Frank Lee [this message]
2018-12-20  7:44 ` 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=CAEExFWuubkuEE57+DPVbwFTw9st6Re72dqtg-JHwQJsxkVF_UA@mail.gmail.com \
    --to=tiny.windzz@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=merez@codeaurora.org \
    --cc=netdev@vger.kernel.org \
    --cc=wil6210@qti.qualcomm.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).