LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Min Li <min.li.xe@renesas.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
	"derek.kiernan@xilinx.com" <derek.kiernan@xilinx.com>,
	"dragan.cvetic@xilinx.com" <dragan.cvetic@xilinx.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"lee.jones@linaro.or" <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 14:49:37 +0000	[thread overview]
Message-ID: <OS3PR01MB6593170DE2F869539E6EDB04BADC9@OS3PR01MB6593.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <YULVDcZ6xfZnPYXd@kroah.com>

> >
> 
> Wait, how can this patch on its own not break things?  Are there no
> in-kernel users of these symbols today?  If not, why is this file in
> here?
> 
> confused,
> 
> greg k-h

Yes, it is standalone now but it would be used by this driver and another PHC driver that I will submit later.

This file provides register definitions and belongs to the MFD change I submitted before. The MFD driver will spawn 2 devices

1) ptp hardware clock device
2) This RSMU misc device

The plan is 

1) submit mfd change
2) submit misc change
3) submit phc change

Min




  reply	other threads:[~2021-09-16 14:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15 18:47 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 ` [PATCH misc v2 1/2] mfd: rsmu: Resolve naming conflict between idt8a340_reg.h and idt82p33_reg.h Greg KH
2021-09-16  5:24 ` Greg KH
2021-09-16 14:49   ` Min Li [this message]
  -- 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=OS3PR01MB6593170DE2F869539E6EDB04BADC9@OS3PR01MB6593.jpnprd01.prod.outlook.com \
    --to=min.li.xe@renesas.com \
    --cc=arnd@arndb.de \
    --cc=derek.kiernan@xilinx.com \
    --cc=dragan.cvetic@xilinx.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=lee.jones@linaro.or \
    --cc=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' \
    /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

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).