linux-mediatek.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Gene Chen <gene.chen.richtek@gmail.com>
Cc: gene_chen@richtek.com, linux-kernel@vger.kernel.org,
	cy_huang@richtek.com, linux-mediatek@lists.infradead.org,
	matthias.bgg@gmail.com, Wilma.Wu@mediatek.com,
	linux-arm-kernel@lists.infradead.org, shufan_lee@richtek.com
Subject: Re: [PATCH v3] mfd: mt6360: add pmic mt6360 driver
Date: Wed, 23 Oct 2019 10:40:43 +0100	[thread overview]
Message-ID: <20191023094043.GB19477@dell> (raw)
In-Reply-To: <CAE+NS36Pdc8zutu=GpNQkREyEu07iLF8NDMtSQcUJE3RuuT2VQ@mail.gmail.com>

On Tue, 22 Oct 2019, Gene Chen wrote:

> 2019-10-16 18:04 GMT+08:00, Lee Jones <lee.jones@linaro.org>:
> > On Tue, 15 Oct 2019, Gene Chen wrote:
> >
> >> Hi Lee,
> >>
> >> we find OF_MFD_CELL is not defined in mfd/core.h, which is ready to
> >> merge to next kernel version
> >> https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next-history/+/master/Next/merge.log
> >
> > It's here:
> >
> > Merging mfd/for-mfd-next (38a6fc63a3ea mfd: db8500-prcmu: Example using new
> > OF_MFD_CELL/MFD_CELL_BASIC MACROs)
> > $ git merge mfd/for-mfd-next
> > Merge made by the 'recursive' strategy.
> >  drivers/mfd/ab8500-core.c    | 138
> > +++++++++++++------------------------------
> >  drivers/mfd/db8500-prcmu.c   |  21 +++----
> >  drivers/mfd/intel-lpss-pci.c |  28 ++++++---
> >  drivers/mfd/ipaq-micro.c     |   6 +-
> >  drivers/mfd/rk808.c          |  22 ++-----
> >  include/linux/mfd/core.h     |  29 +++++++++                <===== [THIS
> > ONE]
> >  include/linux/mfd/rk808.h    |   2 +-
> >  7 files changed, 105 insertions(+), 141 deletions(-)
> >
> > https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next-history/+/master/Next/merge.log#4470
> >
> 
> I thought i need to wait this "mfd/for-mfd-next" patch merge to latest
> codebase, but we can't actually get the date or version (e.g. Linux
> 5.4-rc4) landing
> and i try command "git merge mfd/for-mfd-next" which also can't work
> may i ask how to pull this patch for temporarily build pass?

Rebase onto for-mfd-next or cherry-pick the commit you need.

The tree is located here:

  https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git/

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

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

      reply	other threads:[~2019-10-23  9:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24 15:25 [PATCH v3] mfd: mt6360: add pmic mt6360 driver Gene Chen
2019-10-04 13:33 ` Lee Jones
2019-10-07 18:24   ` Gene Chen
2019-10-15 11:30     ` Gene Chen
2019-10-16 10:04       ` Lee Jones
2019-10-22  8:54         ` Gene Chen
2019-10-23  9:40           ` Lee Jones [this message]

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=20191023094043.GB19477@dell \
    --to=lee.jones@linaro.org \
    --cc=Wilma.Wu@mediatek.com \
    --cc=cy_huang@richtek.com \
    --cc=gene.chen.richtek@gmail.com \
    --cc=gene_chen@richtek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=shufan_lee@richtek.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).