public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: Sergei Antonov <saproj@gmail.com>
Cc: netdev@vger.kernel.org, rmk+kernel@armlinux.org.uk
Subject: Re: Regression: supported_interfaces filling enforcement
Date: Wed, 12 Jul 2023 00:58:48 +0300	[thread overview]
Message-ID: <20230711215848.lhflxqbpyjkmkslj@skbuf> (raw)
In-Reply-To: <CABikg9xc5PryyT+b=3JsJoHppe+tfOs+BWrq+kETQK99A-DG=g@mail.gmail.com>

On Mon, Jul 10, 2023 at 09:09:48PM +0300, Sergei Antonov wrote:
> On Mon, 10 Jul 2023 at 18:38, Vladimir Oltean <olteanv@gmail.com> wrote:
> 
> > That being said, given the kind of bugs I've seen uncovered in this
> > driver recently, I'd say it would be ridiculous to play pretend - you're
> > probably one of its only users. You can probably be a bit aggressive,
> > remove support for incomplete device trees, see if anyone complains, and
> > they do, revert the removal.
> 
> Can mv88e6060 functionality be transferred to mv88e6xxx?

Honestly, I don't know.

  reply	other threads:[~2023-07-11 21:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 14:28 Regression: supported_interfaces filling enforcement Sergei Antonov
2023-07-08 14:01 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-30 16:16   ` Linux regression tracking #update (Thorsten Leemhuis)
2023-07-10 12:35 ` Vladimir Oltean
2023-07-10 14:35   ` Sergei Antonov
2023-07-10 15:38     ` Vladimir Oltean
2023-07-10 18:09       ` Sergei Antonov
2023-07-11 21:58         ` Vladimir Oltean [this message]
2023-07-12  0:58           ` Andrew Lunn
2023-08-09 12:11     ` Russell King (Oracle)
2023-07-13 15:08   ` Russell King (Oracle)
2023-07-25 10:58     ` Linux regression tracking (Thorsten Leemhuis)
2023-07-25 11:26       ` Russell King (Oracle)
2023-07-26 13:45         ` 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=20230711215848.lhflxqbpyjkmkslj@skbuf \
    --to=olteanv@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=saproj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox