From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "H. Nikolaus Schaller" <hns@goldelico.com>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v1] iio: Allow to read mount matrix from ACPI
Date: Wed, 20 Feb 2019 17:08:17 +0000 [thread overview]
Message-ID: <20190220170817.1a6430c4@archlinux> (raw)
In-Reply-To: <20190220161912.GA9224@smile.fi.intel.com>
On Wed, 20 Feb 2019 18:19:12 +0200
Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> On Wed, Feb 20, 2019 at 05:08:52PM +0100, H. Nikolaus Schaller wrote:
> > Hi Andy,
> >
> > > Am 20.02.2019 um 16:20 schrieb Andy Shevchenko <andriy.shevchenko@linux.intel.com>:
> > >
> > > Currently mount matrix is allowed in Device Tree, though there is
> > > no technical issue to extend it to support ACPI.
> > >
> > > Convert the function to use device_property_read_string_array() and
> > > thus allow to read mount matrix from ACPI if available.
> > >
> > > At the same time drop the "of" prefix from its name and
> > > convert current users.
> >
> > Maybe we can drop the "of" prefix after my earlier patches have been accepted?
> >
> > So that you patch does not break compile of my patch series.
>
>
> Whatever Jonathan considers the best for the users and developers!
>
Either way is easy to fix up. We are only talking a rename of a single
function. Keep them separate and I'm sort it out.
Jonathan
prev parent reply other threads:[~2019-02-20 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 15:20 [PATCH v1] iio: Allow to read mount matrix from ACPI Andy Shevchenko
2019-02-20 16:02 ` Jonathan Cameron
2019-02-20 16:41 ` Andy Shevchenko
2019-02-20 17:07 ` Jonathan Cameron
2019-02-20 16:08 ` H. Nikolaus Schaller
2019-02-20 16:19 ` Andy Shevchenko
2019-02-20 17:08 ` 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=20190220170817.1a6430c4@archlinux \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hns@goldelico.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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).