All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
	Vladimir Oltean <olteanv@gmail.com>, Andrew Lunn <andrew@lunn.ch>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: kernel@pengutronix.de, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next v1 1/1] net: dsa: sja1105: silent spi_device_id warnings
Date: Fri, 1 Jul 2022 10:33:43 -0700	[thread overview]
Message-ID: <386c80a0-538f-df32-665c-cd10d62a8db3@gmail.com> (raw)
In-Reply-To: <20220630071013.1710594-1-o.rempel@pengutronix.de>

On 6/30/22 00:10, Oleksij Rempel wrote:
> Add spi_device_id entries to silent following warnings:
>   SPI driver sja1105 has no spi_device_id for nxp,sja1105e
>   SPI driver sja1105 has no spi_device_id for nxp,sja1105t
>   SPI driver sja1105 has no spi_device_id for nxp,sja1105p
>   SPI driver sja1105 has no spi_device_id for nxp,sja1105q
>   SPI driver sja1105 has no spi_device_id for nxp,sja1105r
>   SPI driver sja1105 has no spi_device_id for nxp,sja1105s
>   SPI driver sja1105 has no spi_device_id for nxp,sja1110a
>   SPI driver sja1105 has no spi_device_id for nxp,sja1110b
>   SPI driver sja1105 has no spi_device_id for nxp,sja1110c
>   SPI driver sja1105 has no spi_device_id for nxp,sja1110d
> 
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>

Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
-- 
Florian

  parent reply	other threads:[~2022-07-01 17:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30  7:10 [PATCH net-next v1 1/1] net: dsa: sja1105: silent spi_device_id warnings Oleksij Rempel
2022-06-30 16:10 ` Vladimir Oltean
2022-07-01  7:18   ` Oleksij Rempel
2022-07-01 10:20     ` Vladimir Oltean
2022-07-01 11:04       ` Oleksij Rempel
2022-07-01 17:17 ` Vladimir Oltean
2022-07-01 17:33 ` Florian Fainelli [this message]
2022-07-06 14:43 ` Vladimir Oltean

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=386c80a0-538f-df32-665c-cd10d62a8db3@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=vivien.didelot@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.