From: Lee Jones <lee.jones@linaro.org>
To: min.li.xe@renesas.com
Cc: arnd@arndb.de, gregkh@linuxfoundation.org,
derek.kiernan@xilinx.com, dragan.cvetic@xilinx.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH misc v2 1/2] mfd: rsmu: Resolve naming conflict between idt8a340_reg.h and idt82p33_reg.h
Date: Mon, 20 Sep 2021 09:15:27 +0100 [thread overview]
Message-ID: <YUhDH7ci8jjT2tob@google.com> (raw)
In-Reply-To: <1631808697-25229-1-git-send-email-min.li.xe@renesas.com>
On Thu, 16 Sep 2021, min.li.xe@renesas.com wrote:
> From: Min Li <min.li.xe@renesas.com>
Why have you sent at least 3 v2 submissions?
> Resolve name conflicts so that rsmu misc driver can be simplified to
> one c file suggested by Greg KH
That is not a correctly formatted Suggested-by tag.
> Signed-off-by: Min Li <min.li.xe@renesas.com>
> ---
> Change log
> -resolve name conflicts so that rsmu misc driver can be in one c file suggested by Greg
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2021-09-20 8:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 16:11 [PATCH misc v2 1/2] mfd: rsmu: Resolve naming conflict between idt8a340_reg.h and idt82p33_reg.h min.li.xe
2021-09-16 16:11 ` [PATCH misc v2 2/2] misc: Add Renesas Synchronization Management Unit (SMU) support min.li.xe
2021-09-20 8:15 ` Lee Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-16 15:41 [PATCH misc v2 1/2] mfd: rsmu: Resolve naming conflict between idt8a340_reg.h and idt82p33_reg.h min.li.xe
2021-09-16 15:50 ` Greg KH
2021-09-15 18:47 min.li.xe
2021-09-16 5:23 ` Greg KH
2021-09-16 5:24 ` Greg KH
2021-09-16 14:49 ` Min Li
2021-09-15 18:11 min.li.xe
2021-09-15 18:34 ` Greg KH
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=YUhDH7ci8jjT2tob@google.com \
--to=lee.jones@linaro.org \
--cc=arnd@arndb.de \
--cc=derek.kiernan@xilinx.com \
--cc=dragan.cvetic@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=min.li.xe@renesas.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.