linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: min.li.xe@renesas.com
Cc: arnd@arndb.de, derek.kiernan@xilinx.com,
	dragan.cvetic@xilinx.com, linux-kernel@vger.kernel.org,
	lee.jones@linaro.or
Subject: Re: [PATCH misc v2 1/2] mfd: rsmu: Resolve naming conflict between idt8a340_reg.h and idt82p33_reg.h
Date: Thu, 16 Sep 2021 07:23:50 +0200	[thread overview]
Message-ID: <YULU5g358pqWpqOV@kroah.com> (raw)
In-Reply-To: <1631731629-20862-1-git-send-email-min.li.xe@renesas.com>

On Wed, Sep 15, 2021 at 02:47:08PM -0400, min.li.xe@renesas.com wrote:
> From: Min Li <min.li.xe@renesas.com>
> 
> Signed-off-by: Min Li <min.li.xe@renesas.com>

As I said before, I can not take patches without any changelog text :(

  parent reply	other threads:[~2021-09-16  5:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15 18:47 [PATCH misc v2 1/2] mfd: rsmu: Resolve naming conflict between idt8a340_reg.h and idt82p33_reg.h min.li.xe
2021-09-15 18:47 ` [PATCH misc v2 2/2] misc: Add Renesas Synchronization Management Unit (SMU) support min.li.xe
2021-09-16  5:25   ` Greg KH
2021-09-16 15:33     ` Min Li
2021-09-16 15:39       ` Greg KH
2021-09-16 15:54         ` Min Li
2021-09-16 16:05           ` Greg KH
2021-09-16 17:01             ` Min Li
2021-09-16 17:22               ` Greg KH
2021-09-16 11:31   ` kernel test robot
2021-09-16  5:23 ` Greg KH [this message]
2021-09-16  5:24 ` [PATCH misc v2 1/2] mfd: rsmu: Resolve naming conflict between idt8a340_reg.h and idt82p33_reg.h Greg KH
2021-09-16 14:49   ` Min Li
  -- strict thread matches above, loose matches on Subject: below --
2021-09-16 16:11 min.li.xe
2021-09-20  8:15 ` Lee Jones
2021-09-16 15:41 min.li.xe
2021-09-16 15:50 ` Greg KH
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=YULU5g358pqWpqOV@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=derek.kiernan@xilinx.com \
    --cc=dragan.cvetic@xilinx.com \
    --cc=lee.jones@linaro.or \
    --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 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).