From: Kalle Valo <kalle.valo@iki.fi>
To: Greg KH <gregkh@suse.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/3] Staging: stlc45xx: sync with gitorious git tree
Date: Tue, 09 Jun 2009 07:26:27 +0300 [thread overview]
Message-ID: <87prde2ft8.fsf@litku.valot.fi> (raw)
In-Reply-To: <20090609004532.GA22830@suse.de> (Greg KH's message of "Mon\, 8 Jun 2009 17\:45\:32 -0700")
Greg KH <gregkh@suse.de> writes:
> On Mon, Jun 08, 2009 at 10:09:01PM +0300, Kalle Valo wrote:
>> From: Kalle Valo <kalle.valo@nokia.com>
>>
>> Sync up with stlc45xx repository in gitorious.org from commit
>> bb8675d6e59c34b43618970d37d56d724a5e3d96.
>
> Hm, any reason you smushed 23 patches down into 3? In doing so you lost
> some good information, and some authorship information as well, which is
> not acceptable.
I did shortcuts to avoid the merge hassle. I had some branch trickery
with the gitorious stlc45xx repository which will most probably take
some time to solve.
> So care to send me the 23 patches instead, with the proper authorship
> information?
Sure I can. It might take some time, though.
Please note that slc45xx won't compile in linux-next due to mac80211 API
changes until these patches have been applied.
> And why is development for this driver being done outside the kernel
> tree now that is in it?
These changes have been implemented before stlc45xx was accepted to the
staging tree. They have been just pending on my side.
--
Kalle Valo
next prev parent reply other threads:[~2009-06-09 4:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 19:09 [PATCH 1/3] Staging: stlc45xx: sync with gitorious git tree Kalle Valo
2009-06-08 19:09 ` [PATCH 2/3] Staging: stlc45xx: update mac80211 bss_info_changed() API change Kalle Valo
2009-06-08 19:09 ` [PATCH 3/3] stlc45xx: add TODO Kalle Valo
2009-06-09 0:45 ` [PATCH 1/3] Staging: stlc45xx: sync with gitorious git tree Greg KH
2009-06-09 4:26 ` Kalle Valo [this message]
2009-06-09 7:01 ` Greg KH
2009-06-09 11:31 ` Kalle Valo
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=87prde2ft8.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=gregkh@suse.de \
--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 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.