Linux wireless drivers development
 help / color / mirror / Atom feed
From: Hans Ulli Kroll <ulli.kroll@googlemail.com>
To: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: "Stanislaw Gruszka" <sgruszka@redhat.com>,
	lorenzo.bianconi83@gmail.com, "Felix Fietkau" <nbd@nbd.name>,
	"Jakub Kiciński" <moorray3@wp.pl>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"Hans Ulli Kroll" <ulli.kroll@googlemail.com>,
	"Michal Schmidt" <mschmidt@redhat.com>,
	linux-mediatek@lists.infradead.org
Subject: Re: [ANN] mt76x0 usb driver
Date: Tue, 3 Jul 2018 17:31:04 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1807031725420.3545@T420s> (raw)
In-Reply-To: <CAJ0CqmXE7hF8UAe2iAZ7GhYWb7Uf3zJ+Fg_ervfyK1ojS1Oh=w@mail.gmail.com>

Hi

>
> On Mon, Jun 25, 2018 at 02:55:51PM +0200, Lorenzo Bianconi wrote:

> > Not sure why many integration commits in upstream is a problem. I think
> > having patches posted on mailing list is better than doing them in my
> > "private" tree without any review.
> >
> > > What do you think?
> >
> > I was thinking about posting mt76x0 driver in a subdir (there is sill
> > some cleanup work need to be done there), wait for upstream mt76x2u
> > integration, then post patches that remove duplication between mt76x2
> > and mt76x0 and add support for mt76x0e on the way.
> >
> 
> Ack, fine. I modified a little bit mt76x2u/usb architecture moving
> some parts in common with mt76x0u
> in mt76-usb module (e.g. mt76_queue management in tx_status data path,
> tx_stats workqueue,
> some mcu utility routines). In this way the integration will be easier I guess
> 
> Regards,
> Lorenzo
> 
> > Thanks
> > Stanislaw
> 

I'm currrently working mt76x0u on top of Lorenzo's mt76x2u driver.

Ulli

  reply	other threads:[~2018-07-03 15:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09 14:10 [ANN] mt76x0 usb driver Stanislaw Gruszka
2018-04-09 14:26 ` Lorenzo Bianconi
2018-04-09 14:48   ` Stanislaw Gruszka
2018-04-09 14:53     ` Lorenzo Bianconi
2018-04-09 18:52       ` Hans Ulli Kroll
2018-04-10 10:12       ` Stanislaw Gruszka
2018-06-25 12:08     ` Stanislaw Gruszka
2018-06-25 12:55       ` Lorenzo Bianconi
2018-06-25 13:54         ` Stanislaw Gruszka
2018-06-28 17:26           ` Lorenzo Bianconi
2018-07-03 15:31             ` Hans Ulli Kroll [this message]
2018-07-04 14:00               ` Stanislaw Gruszka
2018-04-09 18:45 ` Hans Ulli Kroll
2018-04-10 10:14   ` Stanislaw Gruszka
2018-04-16 22:30     ` Lorenzo Bianconi

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=alpine.LNX.2.00.1807031725420.3545@T420s \
    --to=ulli.kroll@googlemail.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi83@gmail.com \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=moorray3@wp.pl \
    --cc=mschmidt@redhat.com \
    --cc=nbd@nbd.name \
    --cc=sgruszka@redhat.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