From: Brett Neumeier <bneumeier@gmail.com>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: Neil Brown <neil@brown.name>,
driverdev-devel@linuxdriverproject.org,
Greg Ungerer <gerg@kernel.org>
Subject: Re: [PATCH 0/4] staging: mt7621-pci: Handle minor issues
Date: Fri, 5 Jul 2019 13:43:51 -0500 [thread overview]
Message-ID: <CAGSetNv2adWboHoB4mi9pxgJwbFJhsSmyXegjb7Lc9-H3kiRDQ@mail.gmail.com> (raw)
In-Reply-To: <CAMhs-H_K-mWQYWNUk3xEBc8Ek_128VzZa-Z1ps4yqbDDOZ+=Vg@mail.gmail.com>
On Wed, Jun 26, 2019 at 7:45 AM Sergio Paracuellos
<sergio.paracuellos@gmail.com> wrote:
> No problem, I also miss them rewritting code. That is bad :((.
> > BTW, I applied that on top of your other recent fixes (that ones
> > you pushed to gregkh for staging). So I tested with the
> > updated GPIO reset code.
> Ok, anyway.. I have just sent the change jus to have the same code behaviour
> that was being there before.
FWIW, I have the same results as Greg -- the 4.2 driver works every
time, staging-next frequently hangs.
Out of curiosity, if it's not too complex an answer to go into, what's
the benefit of the staging-next driver? Is there a reason to prefer it
to the 4.2 driver?
--
Brett Neumeier (bneumeier@gmail.com)
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2019-07-05 18:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 6:15 [PATCH 0/4] staging: mt7621-pci: Handle minor issues Sergio Paracuellos
2019-06-21 6:15 ` [PATCH 1/4] staging: mt7621-pci: disable pcie port clock if there is no pcie link Sergio Paracuellos
2019-06-21 6:15 ` [PATCH 2/4] staging: mt7621-pci: add phy exit call if phy_power_on call fails Sergio Paracuellos
2019-06-21 6:15 ` [PATCH 3/4] staging: mt7621-pci-phy: remove disable clock from the phy exit function Sergio Paracuellos
2019-06-21 6:15 ` [PATCH 4/4] staging: mt7621-pci: use 'module_init' instead of 'arch_initcall' Sergio Paracuellos
2019-06-21 12:35 ` [PATCH 0/4] staging: mt7621-pci: Handle minor issues Greg Ungerer
2019-06-21 13:23 ` Sergio Paracuellos
2019-06-23 2:15 ` Brett Neumeier
2019-06-23 5:58 ` Sergio Paracuellos
2019-06-25 5:10 ` Greg Ungerer
2019-06-25 5:18 ` Sergio Paracuellos
2019-06-25 12:47 ` Sergio Paracuellos
2019-06-26 3:31 ` Greg Ungerer
2019-06-26 7:10 ` Sergio Paracuellos
2019-06-26 12:18 ` Greg Ungerer
2019-06-26 12:44 ` Sergio Paracuellos
2019-07-05 18:43 ` Brett Neumeier [this message]
2019-07-06 9:00 ` Sergio Paracuellos
2019-07-06 13:43 ` Brett Neumeier
2019-07-06 16:24 ` Sergio Paracuellos
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=CAGSetNv2adWboHoB4mi9pxgJwbFJhsSmyXegjb7Lc9-H3kiRDQ@mail.gmail.com \
--to=bneumeier@gmail.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gerg@kernel.org \
--cc=neil@brown.name \
--cc=sergio.paracuellos@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.