From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: ChiaEn Wu <peterwu.pub@gmail.com>
Cc: pavel@ucw.cz, lee@kernel.org, matthias.bgg@gmail.com,
chiaen_wu@richtek.com, cy_huang@richtek.com,
linux-leds@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
szunichen@gmail.com,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH v15 RESEND 2/2] leds: flash: mt6370: Add MediaTek MT6370 flashlight support
Date: Thu, 5 Jan 2023 17:08:32 +0200 [thread overview]
Message-ID: <Y7bn8NPyBoBI2HFy@smile.fi.intel.com> (raw)
In-Reply-To: <CABtFH5KjksZ6GSOMafU8aS5mJzGkd8SDGEzH5irFUEFceQTWtQ@mail.gmail.com>
On Thu, Jan 05, 2023 at 06:25:01PM +0800, ChiaEn Wu wrote:
> On Tue, Jan 3, 2023 at 9:06 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
...
> > > obj-$(CONFIG_LEDS_RT8515) += leds-rt8515.o
> > > obj-$(CONFIG_LEDS_SGM3140) += leds-sgm3140.o
> > > +obj-$(CONFIG_LEDS_MT6370_FLASH) += leds-mt6370-flash.o
> >
> > Can it be kept ordered?
>
> hmm... I found "mt6360" actually did not keep the order either...
> Do you want me to put it after "max77693" or after "mt6360"??
Make it most ordered. From above context I can't say which one is the best.
--
With Best Regards,
Andy Shevchenko
WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: ChiaEn Wu <peterwu.pub@gmail.com>
Cc: pavel@ucw.cz, lee@kernel.org, matthias.bgg@gmail.com,
chiaen_wu@richtek.com, cy_huang@richtek.com,
linux-leds@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
szunichen@gmail.com,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH v15 RESEND 2/2] leds: flash: mt6370: Add MediaTek MT6370 flashlight support
Date: Thu, 5 Jan 2023 17:08:32 +0200 [thread overview]
Message-ID: <Y7bn8NPyBoBI2HFy@smile.fi.intel.com> (raw)
In-Reply-To: <CABtFH5KjksZ6GSOMafU8aS5mJzGkd8SDGEzH5irFUEFceQTWtQ@mail.gmail.com>
On Thu, Jan 05, 2023 at 06:25:01PM +0800, ChiaEn Wu wrote:
> On Tue, Jan 3, 2023 at 9:06 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
...
> > > obj-$(CONFIG_LEDS_RT8515) += leds-rt8515.o
> > > obj-$(CONFIG_LEDS_SGM3140) += leds-sgm3140.o
> > > +obj-$(CONFIG_LEDS_MT6370_FLASH) += leds-mt6370-flash.o
> >
> > Can it be kept ordered?
>
> hmm... I found "mt6360" actually did not keep the order either...
> Do you want me to put it after "max77693" or after "mt6360"??
Make it most ordered. From above context I can't say which one is the best.
--
With Best Regards,
Andy Shevchenko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-05 15:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 7:00 [PATCH v15 RESEND 0/2] Add MediaTek MT6370 PMIC support ChiaEn Wu
2023-01-03 7:00 ` ChiaEn Wu
2023-01-03 7:00 ` [PATCH v15 RESEND 1/2] leds: rgb: mt6370: Add MediaTek MT6370 current sink type LED Indicator support ChiaEn Wu
2023-01-03 7:00 ` ChiaEn Wu
2023-01-03 12:45 ` Andy Shevchenko
2023-01-03 12:45 ` Andy Shevchenko
2023-01-10 5:41 ` ChiYuan Huang
2023-01-10 5:41 ` ChiYuan Huang
2023-01-03 7:00 ` [PATCH v15 RESEND 2/2] leds: flash: mt6370: Add MediaTek MT6370 flashlight support ChiaEn Wu
2023-01-03 7:00 ` ChiaEn Wu
2023-01-03 13:05 ` Andy Shevchenko
2023-01-03 13:05 ` Andy Shevchenko
2023-01-05 10:25 ` ChiaEn Wu
2023-01-05 10:25 ` ChiaEn Wu
2023-01-05 15:08 ` Andy Shevchenko [this message]
2023-01-05 15:08 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2022-11-08 3:41 [PATCH v15 RESEND 0/2] Add MediaTek MT6370 PMIC support ChiaEn Wu
2022-11-08 3:41 ` [PATCH v15 RESEND 2/2] leds: flash: mt6370: Add MediaTek MT6370 flashlight support ChiaEn Wu
2022-11-08 3:41 ` ChiaEn Wu
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=Y7bn8NPyBoBI2HFy@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chiaen_wu@richtek.com \
--cc=cy_huang@richtek.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=pavel@ucw.cz \
--cc=peterwu.pub@gmail.com \
--cc=szunichen@gmail.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.