mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Marc Singer <elf@buici.com>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: arm-lh7a40x IDE support in 2.6.6
Date: Fri, 14 May 2004 22:25:19 +0200	[thread overview]
Message-ID: <200405142225.19339.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <20040514205212.A19539@flint.arm.linux.org.uk>

On Friday 14 of May 2004 21:52, Russell King wrote:
> On Fri, May 14, 2004 at 08:45:51PM +0200, Bartlomiej Zolnierkiewicz wrote:
> > On Friday 14 of May 2004 19:26, Marc Singer wrote:
> > > On Fri, May 14, 2004 at 06:40:04PM +0200, Bartlomiej Zolnierkiewicz wrote:
> > > > I was just porting my patches killing <asm/arch/ide.h> for
> > > > ARM to 2.6.6 when noticed that more work is needed now. :-(
> > > >
> > > > arch/arm/mach-lh7a40x/ide-lpd7a40x.c
> > > > include/asm-arm/arch-lh7a40x/ide.h
> > > >
> > > > Why it couldn't be done in drivers/ide/arm
> > > > (as discussed on linux-ide)?
> > >
> > > Your response took look enough for me to switch to another job.  I
> > > haven't yet returned to dealing with this.
> >
> > Yes, it took too long.
> >
> > Anyway, pushing non-working code to mainline is a bad thing
> > (I can show some proofs for this statement).
>
> It was a necessary step.  To get around this, we're going to ask people
> to submit new machine support on a file by file basis, and that's just
> not practical, and you can't expect me to be able to track _every_
> _single_ fscking change to the kernel, and pick up every one in a
> review.

Nobody expects this but expecting people to try building they patches
against latest & greatest kernel before pushing to Linus is sane & practical.
-> ask people to submit patches which are buildable.

> There will always be a delay between changes happening between two people
> and we have to live with it.  Not everyone works on Linus' latest kernel.


      reply	other threads:[~2004-05-14 20:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-14 16:40 Bartlomiej Zolnierkiewicz
2004-05-14 16:52 ` Bartlomiej Zolnierkiewicz
2004-05-14 17:28   ` Marc Singer
2004-05-14 17:26 ` Marc Singer
2004-05-14 18:45   ` Bartlomiej Zolnierkiewicz
2004-05-14 19:47     ` Marc Singer
2004-05-14 21:23       ` Bartlomiej Zolnierkiewicz
2004-05-14 21:33         ` Marc Singer
2004-05-14 22:19           ` Bartlomiej Zolnierkiewicz
2004-05-14 22:49             ` Marc Singer
2004-05-14 23:26               ` Bartlomiej Zolnierkiewicz
2004-05-15  0:10                 ` Marc Singer
2004-05-15  0:25                   ` Bartlomiej Zolnierkiewicz
2004-05-15  0:33                     ` Marc Singer
2004-05-14 19:52     ` Russell King
2004-05-14 20:25       ` Bartlomiej Zolnierkiewicz [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=200405142225.19339.bzolnier@elka.pw.edu.pl \
    --to=b.zolnierkiewicz@elka.pw.edu.pl \
    --cc=elf@buici.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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

all inboxes | Powered by JetHome®