From: David Miller <davem@redhat.com>
To: jiping.ma2@windriver.com
Cc: alexandre.torgue@st.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, joabreu@synopsys.com,
mcoquelin.stm32@gmail.com, peppe.cavallaro@st.com,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] stmmac: debugfs entry name is not be changed when udev rename device name.
Date: Mon, 06 Jan 2020 13:45:57 -0800 (PST) [thread overview]
Message-ID: <20200106.134557.2214546621758238890.davem@redhat.com> (raw)
In-Reply-To: <20200106023341.206459-1-jiping.ma2@windriver.com>
From: Jiping Ma <jiping.ma2@windriver.com>
Date: Mon, 6 Jan 2020 10:33:41 +0800
> Add one notifier for udev changes net device name.
>
> Signed-off-by: Jiping Ma <jiping.ma2@windriver.com>
This doesn't apply to 'net' and since this is a bug fix that is where
you should target this change.
Thank you.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next parent reply other threads:[~2020-01-06 21:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200106023341.206459-1-jiping.ma2@windriver.com>
2020-01-06 21:45 ` David Miller [this message]
[not found] ` <15aedd71-e077-4c6c-e30c-9396d16eaeec@windriver.com>
2020-01-07 2:22 ` [PATCH] stmmac: debugfs entry name is not be changed when udev rename device name David Miller
[not found] ` <99d183bc-7668-7749-54d6-3649c549dec8@windriver.com>
2020-01-07 4:44 ` Florian Fainelli
2020-01-07 21:01 ` David Miller
[not found] <20200102013544.19271-1-jiping.ma2@windriver.com>
2020-01-05 4:18 ` David Miller
[not found] <20191231020302.71792-1-jiping.ma2@windriver.com>
2019-12-31 2:11 ` Randy Dunlap
[not found] ` <719d8dd3-0119-0c93-b299-d2b3d66b1e06@windriver.com>
2019-12-31 2:22 ` Randy Dunlap
2019-12-31 10:12 ` Sergei Shtylyov
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=20200106.134557.2214546621758238890.davem@redhat.com \
--to=davem@redhat.com \
--cc=alexandre.torgue@st.com \
--cc=jiping.ma2@windriver.com \
--cc=joabreu@synopsys.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).