From: David Miller <davem@davemloft.net>
To: timur@codeaurora.org
Cc: arnd@arndb.de, hpuranik@codeaurora.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net: qcom/emac: fix device tree initialization
Date: Tue, 29 May 2018 10:06:44 -0400 (EDT) [thread overview]
Message-ID: <20180529.100644.1020103941854862274.davem@davemloft.net> (raw)
In-Reply-To: <1527384554-14493-1-git-send-email-timur@codeaurora.org>
From: Timur Tabi <timur@codeaurora.org>
Date: Sat, 26 May 2018 20:29:14 -0500
> Commit "net: qcom/emac: Encapsulate sgmii ops under one structure"
> introduced the sgmii_ops structure, but did not correctly initialize
> it on device tree platforms. This resulted in compiler warnings when
> ACPI is not enabled.
>
> Reported-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Timur Tabi <timur@codeaurora.org>
Applied to net-next, thank you.
prev parent reply other threads:[~2018-05-29 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-27 1:29 [PATCH] net: qcom/emac: fix device tree initialization Timur Tabi
2018-05-29 14:06 ` David Miller [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=20180529.100644.1020103941854862274.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arnd@arndb.de \
--cc=hpuranik@codeaurora.org \
--cc=netdev@vger.kernel.org \
--cc=timur@codeaurora.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).