From: David Miller <davem@davemloft.net>
To: weiyj_lk@163.com
Cc: qiang.zhao@nxp.com, yongjun_wei@trendmicro.com.cn,
netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH -next] wan/fsl_ucc_hdlc: remove .owner field for driver
Date: Wed, 20 Jul 2016 14:48:01 -0700 (PDT) [thread overview]
Message-ID: <20160720.144801.1197257804567286578.davem@davemloft.net> (raw)
In-Reply-To: <1468927503-32482-1-git-send-email-weiyj_lk@163.com>
From: Wei Yongjun <weiyj_lk@163.com>
Date: Tue, 19 Jul 2016 11:25:03 +0000
> From: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
>
> Remove .owner field if calls are used which set it automatically.
>
> Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
>
> Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
Applied.
prev parent reply other threads:[~2016-07-20 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 11:25 [PATCH -next] wan/fsl_ucc_hdlc: remove .owner field for driver Wei Yongjun
2016-07-20 21:48 ` David Miller [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=20160720.144801.1197257804567286578.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=qiang.zhao@nxp.com \
--cc=weiyj_lk@163.com \
--cc=yongjun_wei@trendmicro.com.cn \
/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).