From: Jan Kiszka <jan.kiszka@siemens.com>
To: David Miller <davem@davemloft.net>
Cc: peppe.cavallaro@st.com, alexandre.torgue@st.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
andy.shevchenko@gmail.com
Subject: Re: [PATCH v5 0/5] stmmac: pci: Refactor DMI probing
Date: Thu, 22 Jun 2017 19:43:51 +0200 [thread overview]
Message-ID: <5d4f15dc-057c-dbc0-b3cf-27163e4e6347@siemens.com> (raw)
In-Reply-To: <20170622.134031.1966602928075071150.davem@davemloft.net>
On 2017-06-22 19:40, David Miller wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> Date: Thu, 22 Jun 2017 08:17:56 +0200
>
>> Some cleanups of the way we probe DMI platforms in the driver. Reduces
>> a bit of open-coding and makes the logic easier reusable for any
>> potential DMI platform != Quark.
>>
>> Tested on IOT2000 and Galileo Gen2.
>>
>> Changes in v5:
>> - fixed a remaining issue in patch 5
>> - dropped patch 6 for now
>
> Series applied to net-next.
>
> Any chance the DMI table can be marked const as well?
>
Hmm, they are all const - or which one do you mean?
Jan
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2017-06-22 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 6:17 Jan Kiszka
2017-06-22 6:17 ` [PATCH v5 1/5] stmmac: pci: Make stmmac_pci_info structure constant Jan Kiszka
2017-06-22 6:17 ` [PATCH v5 2/5] stmmac: pci: Use stmmac_pci_info for all devices Jan Kiszka
2017-06-22 6:17 ` [PATCH v5 3/5] stmmac: pci: Make stmmac_pci_find_phy_addr truly generic Jan Kiszka
2017-06-22 6:18 ` [PATCH v5 4/5] stmmac: pci: Select quark_pci_dmi_data from quark_default_data Jan Kiszka
2017-06-22 6:18 ` [PATCH v5 5/5] stmmac: pci: Use dmi_system_id table for retrieving PHY addresses Jan Kiszka
2017-06-22 17:40 ` [PATCH v5 0/5] stmmac: pci: Refactor DMI probing David Miller
2017-06-22 17:43 ` Jan Kiszka [this message]
2017-06-22 17:53 ` David Miller
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=5d4f15dc-057c-dbc0-b3cf-27163e4e6347@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=alexandre.torgue@st.com \
--cc=andy.shevchenko@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®