From: "David Rivshin (Allworx)" <drivshin.allworx@gmail.com>
To: David Miller <davem@davemloft.net>, grygorii.strashko@ti.com
Cc: andrew.goodbody@cambrionix.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
mugunthanvnm@ti.com, tony@atomide.com
Subject: Re: [PATCH v2 1/1] drivers: net: cpsw: Prevent NUll pointer dereference with two PHYs
Date: Tue, 19 Apr 2016 19:38:08 -0400 [thread overview]
Message-ID: <20160419193808.29dc51c3.drivshin.allworx@gmail.com> (raw)
In-Reply-To: <20160419.184339.1558043853032502121.davem@davemloft.net>
On Tue, 19 Apr 2016 18:43:39 -0400 (EDT)
David Miller <davem@davemloft.net> wrote:
> From: Grygorii Strashko <grygorii.strashko@ti.com>
> Date: Tue, 19 Apr 2016 21:44:09 +0300
>
> > May be you can send revert + your patch 1 (only fix for this issue).
> >
> > Dave, Does that sound good to you?
>
> Sure.
OK, I will hopefully have that ready tomorrow evening.
Anything in particular I should mention in the revert commit message?
I didn't find a discussion on it, other than the earlier statement that
"it breaks boot on many TI boards".
next prev parent reply other threads:[~2016-04-19 23:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 13:56 [PATCH v2 0/1] drivers: net: cpsw: Fix NULL pointer dereference with two slave PHYs Andrew Goodbody
2016-04-19 13:56 ` [PATCH v2 1/1] drivers: net: cpsw: Prevent NUll pointer dereference with two PHYs Andrew Goodbody
2016-04-19 14:41 ` Grygorii Strashko
2016-04-19 15:01 ` David Rivshin (Allworx)
2016-04-19 15:44 ` Grygorii Strashko
2016-04-19 17:14 ` David Rivshin (Allworx)
2016-04-19 17:44 ` Florian Fainelli
2016-04-19 18:44 ` Grygorii Strashko
2016-04-19 22:43 ` David Miller
2016-04-19 23:38 ` David Rivshin (Allworx) [this message]
2016-04-20 9:37 ` Grygorii Strashko
2016-04-19 16:05 ` 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=20160419193808.29dc51c3.drivshin.allworx@gmail.com \
--to=drivshin.allworx@gmail.com \
--cc=andrew.goodbody@cambrionix.com \
--cc=davem@davemloft.net \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.org \
--cc=tony@atomide.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