From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [git pull] IDE updates #4
Date: Fri, 24 Oct 2008 02:13:06 +0400 [thread overview]
Message-ID: <4900F6F2.6000601@ru.mvista.com> (raw)
In-Reply-To: <200810232307.15462.bzolnier@gmail.com>
Hello.
Bartlomiej Zolnierkiewicz wrote:
>>>> Also I didn't know anything about your patchset and its
>>>> dependency on TX4939, otherwise I'll be pushing things in
>>>>
>>> The patchset consists of a large patch moving read_sff_dma_status() to
>>> its porper place, one small preparatory patch, and 2 followup patches,
>>> so unfortunately it's dependent on TX4939 in its main patch (worse, the
>>> relevant part of this driver has changed after your last merged driver
>>> version)...
>>>
>>>> different order or even skip this pull request if needed
>>>> (TX493x drivers are new stuff and were still under review,
>>>> such things can be also submitted after the merge window
>>>> closes so they were given the lowest priority).
>>>>
>>> Unfortunately, that driver has been submitted first back 9/09, long
>>> before my patchset was even created, so the dependence was just natural.
>>>
>> I could also rip out TX4939 part from the patch and leave Atsushi to deal
>> with the fallout (though I could give him the ripped out part to simply be
>> merged to the driver) if you would queue my patchset ahead of the driver.
>> Though I feel it's too late now for my patchset to get into 2.6.28 the way
>> things have been happening... :-/
>>
>
> Ehm, submitting things _before_ the merge window usually help. ;-)
>
If I only had time to do that...
> Anyway, no need to get too frustrated over it. It is normal that
>
I got used to my bad luck long ago -- this was only a minor series of
misfortunes... :-)
MBR, Sergei
prev parent reply other threads:[~2008-10-23 22:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 19:00 [git pull] IDE updates #4 Bartlomiej Zolnierkiewicz
2008-10-21 19:18 ` Sergei Shtylyov
2008-10-23 21:13 ` Bartlomiej Zolnierkiewicz
2008-10-22 11:49 ` Sergei Shtylyov
2008-10-22 12:14 ` Bartlomiej Zolnierkiewicz
2008-10-22 12:44 ` Sergei Shtylyov
2008-10-22 21:37 ` Bartlomiej Zolnierkiewicz
2008-10-22 22:56 ` Sergei Shtylyov
2008-10-23 15:57 ` Sergei Shtylyov
2008-10-23 21:07 ` Bartlomiej Zolnierkiewicz
2008-10-23 22:13 ` Sergei Shtylyov [this message]
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=4900F6F2.6000601@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).