From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Serge Semin <Sergey.Semin@baikalelectronics.ru>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Serge Semin <fancer.lancer@gmail.com>,
Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Robert Jarzmik <robert.jarzmik@free.fr>
Subject: Re: [PATCH v1 1/3] spi: dln2: Propagate firmware node
Date: Wed, 22 Dec 2021 17:51:24 +0200 [thread overview]
Message-ID: <YcNJfKVTrU0ZAfL5@smile.fi.intel.com> (raw)
In-Reply-To: <YcNEz2MaigJp0UAe@sirena.org.uk>
On Wed, Dec 22, 2021 at 03:31:27PM +0000, Mark Brown wrote:
> On Wed, Dec 22, 2021 at 03:54:21PM +0200, Andy Shevchenko wrote:
> > Propagate firmware node by using a specific API call, i.e. device_set_node().
> cc1: all warnings being treated as errors
Oops, I was in full impression that I have it enabled, but no, the other two
only. I'll fix this ASAP, sorry for that, I have added the configuration
option.
--
With Best Regards,
Andy Shevchenko
WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Serge Semin <Sergey.Semin@baikalelectronics.ru>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Serge Semin <fancer.lancer@gmail.com>,
Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Robert Jarzmik <robert.jarzmik@free.fr>
Subject: Re: [PATCH v1 1/3] spi: dln2: Propagate firmware node
Date: Wed, 22 Dec 2021 17:51:24 +0200 [thread overview]
Message-ID: <YcNJfKVTrU0ZAfL5@smile.fi.intel.com> (raw)
In-Reply-To: <YcNEz2MaigJp0UAe@sirena.org.uk>
On Wed, Dec 22, 2021 at 03:31:27PM +0000, Mark Brown wrote:
> On Wed, Dec 22, 2021 at 03:54:21PM +0200, Andy Shevchenko wrote:
> > Propagate firmware node by using a specific API call, i.e. device_set_node().
> cc1: all warnings being treated as errors
Oops, I was in full impression that I have it enabled, but no, the other two
only. I'll fix this ASAP, sorry for that, I have added the configuration
option.
--
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:[~2021-12-22 15:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 13:54 [PATCH v1 1/3] spi: dln2: Propagate firmware node Andy Shevchenko
2021-12-22 13:54 ` Andy Shevchenko
2021-12-22 13:54 ` [PATCH v1 2/3] spi: dw: " Andy Shevchenko
2021-12-22 13:54 ` Andy Shevchenko
2021-12-22 13:54 ` [PATCH v1 3/3] spi: pxa2xx: " Andy Shevchenko
2021-12-22 13:54 ` Andy Shevchenko
2021-12-22 15:31 ` [PATCH v1 1/3] spi: dln2: " Mark Brown
2021-12-22 15:31 ` Mark Brown
2021-12-22 15:51 ` Andy Shevchenko [this message]
2021-12-22 15:51 ` Andy Shevchenko
2021-12-23 17:17 ` Mark Brown
2021-12-23 17:17 ` Mark Brown
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=YcNJfKVTrU0ZAfL5@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=broonie@kernel.org \
--cc=daniel@zonque.org \
--cc=fancer.lancer@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
/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.