From: Greg Dietsche <greg@gregd.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>, linux-wireless@vger.kernel.org
Subject: Re: pull request: iwlegacy 2011-09-14
Date: Mon, 19 Sep 2011 17:24:41 -0500 [thread overview]
Message-ID: <4E77C129.7070203@gregd.org> (raw)
In-Reply-To: <20110919193122.GD2608@tuxdriver.com>
On Mon, 19 Sep 2011 15:31:22 -0400, John W. Linville wrote:
> On Wed, Sep 14, 2011 at 10:59:16AM +0200, Stanislaw Gruszka wrote:
>> John,
>>
>> Please pull iwlegacy cleanup changes done by Greg and me, intended
>> for 3.2. These request include huge patches with file renaming and
>> automatic code processing done by sed and indent. Work of changing
>> iwlegacy driver into something that I could consider maintainable
>> is not done yet, but these massive changes bring closer into that.
>> Hopefully with having clean, maintainable code I will be able to
>> fix some nasty, not easy reproducible bugs, we still have in the
>> iwlegacy driver.
>>
>> Thanks.
>>
>> The following changes since commit
>> d82cdad64a0127611724c61849a8487d69fb76ef:
>>
>> Merge branch 'master' of
>> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next
>> (2011-08-30 16:34:33 -0400)
>>
>> are available in the git repository at:
>>
>> git://github.com/dietsche/linux.git
>> wireless-next-iwlegacy-stanislaw-greg
>
> It looks like you pulled something other than wireless-next into this
> tree. If you want me to pull directly, then you need to based your
> tree (or at least the branch I'm pulling) on wireless-next
> exclusively.
Sorry for the confusing branch name! I was naming it based on which
kernel release the code is for and not where it was branched from. Also,
I hadn't anticipated that my git tree might end up in pull request...
The branch wireless-next-iwlegacy-stanislaw-greg is based on John's
wireless-testing tree. Looking at previous emails in this thread, we
referred to wireless-testing as the base for the changes, so branching
from wireless-testing was done on purpose.
I briefly tried to apply the patch set to wireless-next, but it doesn't
like Stanislaw's second patch (rename iwl to il). So some work will need
to be done if we really need to pull into wireless-next.
I'm not real familiar with the pull process... so let me know if you'd
like me to do something.
Greg
next prev parent reply other threads:[~2011-09-19 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 8:59 pull request: iwlegacy 2011-09-14 Stanislaw Gruszka
2011-09-19 19:31 ` John W. Linville
2011-09-19 22:24 ` Greg Dietsche [this message]
2011-09-19 22:59 ` Greg Dietsche
2011-09-20 7:18 ` Stanislaw Gruszka
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=4E77C129.7070203@gregd.org \
--to=greg@gregd.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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;
as well as URLs for NNTP newsgroup(s).