From: Andrew Lunn <andrew@lunn.ch>
To: Meng Tang <tangmeng@uniontech.com>
Cc: kvalo@kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipw2x00: use DEVICE_ATTR_*() macro
Date: Fri, 1 Apr 2022 15:09:21 +0200 [thread overview]
Message-ID: <Ykb5gajW19kkO15N@lunn.ch> (raw)
In-Reply-To: <20220401053138.17749-1-tangmeng@uniontech.com>
On Fri, Apr 01, 2022 at 01:31:38PM +0800, Meng Tang wrote:
> Use DEVICE_ATTR_*() helper instead of plain DEVICE_ATTR,
> which makes the code a bit shorter and easier to read.
Hi Meng
Thanks for doing what i suggested. Looks good.
Please take a look at https://docs.kernel.org/networking/netdev-FAQ.html
There are a few process issues to work out, like the branch name in
the subject, and that the merge window is currently closed so you will
need to repost next week.
Andrew
prev parent reply other threads:[~2022-04-01 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 5:31 Meng Tang
2022-04-01 13:09 ` Andrew Lunn [this message]
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=Ykb5gajW19kkO15N@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tangmeng@uniontech.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
all inboxes | Powered by JetHome®