From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Okan Sahin <okan.sahin@analog.com>,
outreachy@lists.linux.dev, Lee Jones <lee@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Caleb Connolly <caleb.connolly@linaro.org>,
Ramona Bolboaca <ramona.bolboaca@analog.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
ChiYuan Huang <cy_huang@richtek.com>,
Anand Ashok Dumbre <anand.ashok.dumbre@xilinx.com>,
William Breathitt Gray <william.gray@linaro.org>,
Manish Narani <manish.narani@xilinx.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 0/5] staging: drivers: mfd: Add MAX77541 MFD and related device drivers
Date: Sun, 11 Dec 2022 14:07:27 +0000 [thread overview]
Message-ID: <20221211140727.6da705ac@jic23-huawei> (raw)
In-Reply-To: <Y5XcUtNInUJl98JP@smile.fi.intel.com>
On Sun, 11 Dec 2022 15:34:10 +0200
Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> On Sun, Dec 11, 2022 at 12:20:43PM +0000, Jonathan Cameron wrote:
> > On Wed, 7 Dec 2022 13:09:34 +0200
> > Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> > > On Wed, Dec 07, 2022 at 12:08:39PM +0300, Okan Sahin wrote:
> > > > This patchset adds mfd, regulator and adc driver and related bindings.The patches
> > > > are required to be applied in sequence.
> > >
> > > You have an indentation / wrapping issues in the above text.
> > >
> > > Nevertheless, why staging? What does it mean?
> >
> > The main reason to go via staging is because a driver is sitting out
> > of tree and it is useful to bring it in on the basis that it can then be
> > cleaned up in tree before moving out of staging.
>
> But files are not in staging. Me being confused.
I noticed that when I got to the patches :)
Odd indeed - I'm guessing some cut and paste gone wrong.
Jonathan
>
> > For a relatively small driver like this, that's hard to argue. Just
> > clean it up in response to review feedback and then we can take it
> > directly into relevant subsystems in the main tree.
>
prev parent reply other threads:[~2022-12-11 13:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 9:08 [PATCH 0/5] staging: drivers: mfd: Add MAX77541 MFD and related device drivers Okan Sahin
2022-12-07 9:08 ` [PATCH 1/5] staging: drivers: mfd: Add MAX77541/MAX77540 PMIC Support Okan Sahin
2022-12-07 11:24 ` Andy Shevchenko
2022-12-11 12:36 ` Jonathan Cameron
2022-12-07 9:08 ` [PATCH 2/5] staging: dt-bindings: mfd: adi,max77541.yaml Add MAX77541 bindings Okan Sahin
2022-12-07 10:05 ` Krzysztof Kozlowski
2022-12-07 14:19 ` Rob Herring
2022-12-07 9:08 ` [PATCH 3/5] staging: drivers: regulator: Add MAX77541 Regulator Support Okan Sahin
2022-12-07 11:16 ` Andy Shevchenko
2022-12-11 12:48 ` Jonathan Cameron
2022-12-07 9:08 ` [PATCH 4/5] staging: dt-bindings: regulator: adi,max77541.yaml Add MAX77541 Regulator bindings Okan Sahin
2022-12-07 10:07 ` Krzysztof Kozlowski
2022-12-07 14:19 ` Rob Herring
2022-12-07 9:08 ` [PATCH 5/5] staging: drivers: iio: adc: Adc MAX77541 ADC Support Okan Sahin
2022-12-07 11:30 ` Andy Shevchenko
2022-12-07 12:49 ` kernel test robot
2022-12-11 13:01 ` Jonathan Cameron
2022-12-07 11:09 ` [PATCH 0/5] staging: drivers: mfd: Add MAX77541 MFD and related device drivers Andy Shevchenko
2022-12-11 12:20 ` Jonathan Cameron
2022-12-11 13:34 ` Andy Shevchenko
2022-12-11 14:07 ` Jonathan Cameron [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=20221211140727.6da705ac@jic23-huawei \
--to=jic23@kernel.org \
--cc=anand.ashok.dumbre@xilinx.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=caleb.connolly@linaro.org \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manish.narani@xilinx.com \
--cc=okan.sahin@analog.com \
--cc=outreachy@lists.linux.dev \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=ramona.bolboaca@analog.com \
--cc=robh+dt@kernel.org \
--cc=william.gray@linaro.org \
/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).