From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [git pull] IDE updates #4
Date: Wed, 22 Oct 2008 23:37:42 +0200 [thread overview]
Message-ID: <200810222337.42218.bzolnier@gmail.com> (raw)
In-Reply-To: <48FF2047.6000509@ru.mvista.com>
On Wednesday 22 October 2008, Sergei Shtylyov wrote:
> Hello.
>
> Bartlomiej Zolnierkiewicz wrote:
>
> >>> Remove needless/confusing subdirs from drivers/ide/.
> >> I think that with 2 new drivers being submitted/reworked based on feedback
> >> and several patches submitted and pending submission to the pata-2.6 series
> >> this really could have waited till 2.6.29...
> >>
> >
> > The situation is perfect right now for this change as there are no outstanding
> > patches in pata-2.6 tree
>
> There was one patch (already stale TX4939 version driver) as of
> yesterday.
Indeed.
> > and number of new submitted patches is < 10 (I'll take
> > care of fixing them up, ditto for all other new stuff that will be using old
> > naming scheme).
> >
>
> Thanks for clarifying this.
> This rename only added more uncertainty for my pending patchset
> (which had been already dependant on at least TX4939 driver which keeps
> being recast by Atsushi and being stale in pata-2.6 series) as I can't
> predict when you and Linus will merge the changes and this is getting on
> my nerves, as I don't have time on any extra rework and I'm running out
> of time with the submission. I know I should have done this earlier and
Maybe some parts could be submitted separately?
(so keeping them up-to-date in pata-2.6 would be my task)
Also I didn't know anything about your patchset and its
dependency on TX4939, otherwise I'll be pushing things in
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).
Please ping me about such issues, I'm certainly willing to
adjust my workflow if this is going to help other people with
their work but I can't do much if I don't know anything...
> I'd have done this if its not for my unfortunate vacations... I aslso
> kept finding new issues looking on the IOC4 driver. :-/
I remember about your SGIIOC4 fixes and they are going to
make the next git pull request so sooner this one gets in the
better. Also maybe you could get some help with fixing this
driver from SGI folks if there are still some issues left?
Thanks,
Bart
next prev parent reply other threads:[~2008-10-22 21:40 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 [this message]
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
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=200810222337.42218.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sshtylyov@ru.mvista.com \
--cc=torvalds@linux-foundation.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).