All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, a.zummo@towertech.it,
	alexandre.belloni@bootlin.com, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org,
	stefan@agner.ch, b.galvani@gmail.com, phh@phh.me,
	letux-kernel@openphoenux.org
Subject: Re: [PATCH v3 2/6] mfd: rn5t618: prepare for irq handling
Date: Wed, 11 Dec 2019 07:44:00 +0000	[thread overview]
Message-ID: <20191211074400.GV3468@dell> (raw)
In-Reply-To: <20191210173146.6b31e599@kemnade.info>

On Tue, 10 Dec 2019, Andreas Kemnade wrote:

> accidently send it only to Lee, that was unintended.
> 
> On Tue, 10 Dec 2019 09:13:51 +0000
> Lee Jones <lee.jones@linaro.org> wrote:
> 
> > On Fri, 29 Nov 2019, Andreas Kemnade wrote:
> > 
> > > rn5t618 currently lacks irq handling. To prepare implementation  
> > 
> > "RN5T618"
> > "IRQ"
> > 
> > > in a rn5t618-irq.c, move main file to rn5t618-core.c  
> > 
> > Why do you *need* to call it "core"?
> > 
> Well, the pattern is that irq stuff is in a separate file
> for other mfds. And when I want to link things together to a rn5t618.[k]o
> I think that none objects cannot be called rn5t618.o and so no source
> file rn5t618.o. Am I wrong here? Of course if things can live in one file
> this thing is not needed.

Unless you have a good reason for separating out the code, having it
all in a single file is preferred.

> > > Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
> > > ---
> > >  drivers/mfd/Makefile                      | 2 ++
> > >  drivers/mfd/{rn5t618.c => rn5t618-core.c} | 0
> > >  2 files changed, 2 insertions(+)
> > >  rename drivers/mfd/{rn5t618.c => rn5t618-core.c} (100%)
> > > 
> > > diff --git a/drivers/mfd/Makefile b/drivers/mfd/Makefile
> > > index c1067ea46204..110ea700231b 100644
> > > --- a/drivers/mfd/Makefile
> > > +++ b/drivers/mfd/Makefile
> > > @@ -216,6 +216,8 @@ obj-$(CONFIG_MFD_PALMAS)	+= palmas.o
> > >  obj-$(CONFIG_MFD_VIPERBOARD)    += viperboard.o
> > >  obj-$(CONFIG_MFD_RC5T583)	+= rc5t583.o rc5t583-irq.o
> > >  obj-$(CONFIG_MFD_RK808)		+= rk808.o
> > > +
> > > +rn5t618-objs			:= rn5t618-core.o
> > >  obj-$(CONFIG_MFD_RN5T618)	+= rn5t618.o
> > >  obj-$(CONFIG_MFD_SEC_CORE)	+= sec-core.o sec-irq.o
> > >  obj-$(CONFIG_MFD_SYSCON)	+= syscon.o
> > > diff --git a/drivers/mfd/rn5t618.c b/drivers/mfd/rn5t618-core.c
> > > similarity index 100%
> > > rename from drivers/mfd/rn5t618.c
> > > rename to drivers/mfd/rn5t618-core.c  
> > 



-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2019-12-11  7:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29 21:20 [PATCH v3 0/6] Add rtc support for rn5t618 mfd Andreas Kemnade
2019-11-29 21:20 ` [PATCH v3 1/6] dt-bindings: mfd: rn5t618: Document optional property interrupts Andreas Kemnade
2019-12-10  8:52   ` Lee Jones
2019-11-29 21:20 ` [PATCH v3 2/6] mfd: rn5t618: prepare for irq handling Andreas Kemnade
2019-12-10  9:13   ` Lee Jones
2019-12-10 17:06     ` Andreas Kemnade
2019-12-11  7:44       ` Lee Jones [this message]
2019-11-29 21:20 ` [PATCH v3 3/6] mfd: rn5t618: add irq support Andreas Kemnade
2019-12-10  9:32   ` Lee Jones
2019-12-10 16:59     ` Andreas Kemnade
2019-12-11  7:50       ` Lee Jones
2019-12-11 11:43         ` Andreas Kemnade
2019-11-29 21:20 ` [PATCH v3 4/6] mfd: rn5t618: add rtc related registers Andreas Kemnade
2019-11-29 21:20 ` [PATCH v3 5/6] mfd: rn5t618: add more subdevices Andreas Kemnade
2019-11-29 21:20 ` [PATCH v3 6/6] rtc: rtc-rc5t619: add ricoh rc5t619 RTC driver Andreas Kemnade
2019-12-02  9:39   ` Alexandre Belloni
2019-12-11 19:33     ` Andreas Kemnade
2019-12-11 20:17       ` Alexandre Belloni

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=20191211074400.GV3468@dell \
    --to=lee.jones@linaro.org \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andreas@kemnade.info \
    --cc=b.galvani@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=letux-kernel@openphoenux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=phh@phh.me \
    --cc=robh+dt@kernel.org \
    --cc=stefan@agner.ch \
    /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.