linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: linux-wireless@vger.kernel.org, Larry.Finger@lwfinger.net
Subject: Re: [PATCH 1/1] New driver: rtl8723au (mac80211)
Date: Tue, 29 Sep 2015 11:56:46 +0300	[thread overview]
Message-ID: <87io6t7gdt.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <wrfjlhcidq9b.fsf@redhat.com> (Jes Sorensen's message of "Mon, 07 Sep 2015 14:43:28 -0400")

Jes Sorensen <Jes.Sorensen@redhat.com> writes:

>>>> I doubt that this will be in active enough development that a separate
>>>> git tree is needed. wireless-drivers trees should be enough and this
>>>> line can be removed.
>>>
>>> I would like to keep this line, it points to my development tree, which
>>> allows users to go back and look through my full development logs, as
>>> well as see ongoing work before it's pushed upstream.
>>
>> I prefer that wireless-drivers(-next).git is used as the baseline for
>> wireless driver patches, so please remove this tag. You can document
>> your git server in the wiki, commit log and so on.
>
> I will insist on keeping my branch listed as long as I maintain the
> driver. Other drivers do the same thing, like iwlwifi. I'm happy to send
> you patches against wireless-drivers-next.git though.

To keep things simple for me I want that the patches are based on
wireless-drivers-next.git. iwlwifi is under so active development that
an extra tree is justified, but having a dedicated tree for a not so
active driver is just extra work for me which I do not want to have.

With rtlwifi it goes so that Larry acks the patches on the list and
patchwork automatically adds the ack to the commit log when I apply the
patch, which is easy and fast for everyone. The same should go with
rtl8723au.

-- 
Kalle Valo

  parent reply	other threads:[~2015-09-29  8:56 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 20:24 [PATCH v3 0/1] New driver: rtl8723au (mac80211) Jes.Sorensen
2015-03-23 20:25 ` [PATCH 1/1] " Jes.Sorensen
2015-03-23 22:51   ` Joe Perches
2015-03-24  1:25     ` Jes Sorensen
2015-04-28  8:37   ` Kalle Valo
2015-04-28 12:55     ` Kalle Valo
2015-04-28 14:27     ` Jes Sorensen
2015-04-28 15:15       ` Larry Finger
2015-09-06 13:38       ` Kalle Valo
2015-09-06 16:41         ` Larry Finger
2015-09-07 13:37           ` Kalle Valo
2015-09-07 18:43         ` Jes Sorensen
2015-09-07 18:50           ` Larry Finger
2015-09-09 14:16             ` Jes Sorensen
2015-09-29  8:56           ` Kalle Valo [this message]
2015-09-29 10:42             ` Jes Sorensen
  -- strict thread matches above, loose matches on Subject: below --
2015-05-05 20:04 Xose Vazquez Perez
2015-05-05 21:40 ` Jes Sorensen
2015-05-07  9:43   ` Xose Vazquez Perez
2015-05-07 15:43     ` Larry Finger
2015-03-09 17:00 [PATCH v2 0/1] " Jes.Sorensen
2015-03-09 17:00 ` [PATCH 1/1] " Jes.Sorensen
2015-03-09 17:46   ` Johannes Berg
2015-03-09 18:35     ` Jes Sorensen
2015-03-09 19:52       ` Johannes Berg
2015-03-09 18:20   ` Joe Perches
2015-03-09 18:43     ` Jes Sorensen
2015-03-09 18:51       ` Joe Perches
2015-03-09 19:02         ` Jes Sorensen
2015-03-09 19:07           ` Joe Perches
2015-03-06 22:15 [PATCH 0/1] " Jes.Sorensen
2015-03-06 22:15 ` [PATCH 1/1] " Jes.Sorensen
2015-03-06 22:59   ` Joe Perches
2015-03-07  5:18     ` Jes Sorensen
2015-03-07  5:23       ` Joe Perches
2015-03-07  5:33         ` Jes Sorensen
2015-03-07 21:30   ` Larry Finger
2015-03-09 17:08     ` Jes Sorensen

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=87io6t7gdt.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=Jes.Sorensen@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    /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).