From: Lee Jones <lee.jones@linaro.org>
To: Tianfei Zhang <tianfei.zhang@intel.com>
Cc: yilun.xu@intel.com, hao.wu@intel.com, trix@redhat.com,
linux-kernel@vger.kernel.org, linux-fpga@vger.kernel.org,
russell.h.weight@intel.com, matthew.gerlach@linux.intel.com
Subject: Re: [PATCH v2 1/4] mfd: intel-m10-bmc: rename the local variables
Date: Mon, 27 Jun 2022 14:49:47 +0100 [thread overview]
Message-ID: <Yrm1e+kC/lo8PwDS@google.com> (raw)
In-Reply-To: <20220617020405.128352-2-tianfei.zhang@intel.com>
On Thu, 16 Jun 2022, Tianfei Zhang wrote:
> It had better use ddata for local variables which
> directly interacts with dev_get_drvdata()/dev_set_drvdata().
>
> Signed-off-by: Tianfei Zhang <tianfei.zhang@intel.com>
> ---
> drivers/mfd/intel-m10-bmc.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
For my own reference (apply this as-is to your sign-off block):
Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>
--
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2022-06-27 13:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 2:04 [PATCH v2 0/4] add PMCI driver support Tianfei Zhang
2022-06-17 2:04 ` [PATCH v2 1/4] mfd: intel-m10-bmc: rename the local variables Tianfei Zhang
2022-06-27 13:49 ` Lee Jones [this message]
2022-06-17 2:04 ` [PATCH v2 2/4] mfd: intel-m10-bmc: split into core and spi Tianfei Zhang
2022-06-20 9:58 ` Xu Yilun
2022-06-21 0:56 ` Zhang, Tianfei
2022-06-17 2:04 ` [PATCH v2 3/4] mfd: intel-m10-bmc: add PMCI driver Tianfei Zhang
2022-06-20 11:55 ` Xu Yilun
2022-06-21 1:55 ` Zhang, Tianfei
2022-06-17 2:04 ` [PATCH v2 4/4] mfd: intel-m10-bmc: support multiple register layouts Tianfei Zhang
2022-06-20 14:19 ` Xu Yilun
2022-06-21 2:05 ` Zhang, Tianfei
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=Yrm1e+kC/lo8PwDS@google.com \
--to=lee.jones@linaro.org \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@linux.intel.com \
--cc=russell.h.weight@intel.com \
--cc=tianfei.zhang@intel.com \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.