public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcin Dalecki <dalecki@evision.ag>
To: unlisted-recipients:; (no To-header on input)
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pdc20265 problem.
Date: Fri, 09 Aug 2002 08:44:18 +0200	[thread overview]
Message-ID: <3D5364C2.9030106@evision.ag> (raw)
In-Reply-To: Pine.LNX.4.10.10208081052270.25573-100000@master.linux-ide.org

Uz.ytkownik Andre Hedrick napisa?:
> Because I can not get a FSCKING PATCH past any of the Lead Penquins.
> 
> /src/linux-2.5.4-pristine/drivers/ide/ide-pci.c
> #ifdef CONFIG_PDC202XX_FORCE
>         {DEVID_PDC20265,"PDC20265",     PCI_PDC202XX,   ATA66_PDC202XX,
> INIT_PDC202XX,  NULL,           {{0x00,0x00,0x00}, {0x00,0x00,0x00}},
> ON_BOARD,
> 48 },
> #else /* !CONFIG_PDC202XX_FORCE */
>         {DEVID_PDC20265,"PDC20265",     PCI_PDC202XX,   ATA66_PDC202XX,
> INIT_PDC202XX,  NULL,           {{0x50,0x02,0x02}, {0x50,0x04,0x04}},
> OFF_BOARD,
> 48 },
> #endif
> 
> But since there is the option to compile off-board as bootable, it is a
> noop.  I have not been able to directly add code or update any kernel
> first hand since the change in 2.5.3 and my exit of Linux Development at
> 2.5.5.  So I really don't give a damn.
> 
> But what I do know is people bug me for patches and updates and ask me to
> fix 2.5.XX on a regular bases.  Nobody takes my patches but man when crap
> hits the fan they come running for me to put it right again.

Bullshit. First you have to send patches out at all before they can be
accepted or rejected. As far as I'm concerned I never saw anything from
him.


  reply	other threads:[~2002-08-09  6:45 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-02 19:05 [PATCH] pdc20265 problem Bartlomiej Zolnierkiewicz
2002-08-02 23:05 ` Marcelo Tosatti
2002-08-03  0:55   ` Bartlomiej Zolnierkiewicz
2002-08-03  0:08     ` Marcelo Tosatti
2002-08-03 15:37       ` [PATCH] " Nick Orlov
2002-08-03 18:29         ` Nick Orlov
2002-08-03  1:22     ` Nick Orlov
2002-08-03 13:41       ` Alan Cox
2002-08-06  3:48     ` Bill Davidsen
2002-08-06  4:33       ` Nick Orlov
2002-08-07  3:09         ` Bill Davidsen
2002-08-07  3:56           ` Nick Orlov
2002-08-07 18:30             ` Andre Hedrick
2002-08-07 20:27               ` Tomas Szepe
2002-08-07 22:46             ` Bill Davidsen
2002-08-08 10:50               ` Andre Hedrick
2002-08-08 17:42                 ` Nick Orlov
2002-08-08 18:02                   ` Andre Hedrick
2002-08-09  6:44                     ` Marcin Dalecki [this message]
2002-08-12  1:37                       ` Andre Hedrick
2002-08-09 17:16                 ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2002-08-08 18:22 Petr Vandrovec
2002-08-08 18:35 ` Andre Hedrick
2002-08-09  6:47   ` Marcin Dalecki
2002-08-12  1:24     ` Andre Hedrick
2002-08-08 16:48 Petr Vandrovec
2002-08-08 17:30 ` Andre Hedrick
2002-08-08 12:45 Petr Vandrovec
2002-08-08 13:02 ` Andre Hedrick
2002-08-07 18:39 Adam J. Richter
2002-08-07 19:33 ` Thunder from the hill
2002-08-07 21:11   ` Alan Cox
2002-08-07 20:02     ` Thunder from the hill
2002-08-07 23:40       ` Alan Cox
2002-08-07 10:20 Petr Vandrovec
2002-08-07 23:04 ` Bill Davidsen
2002-08-07  7:54 Adam J. Richter
2002-08-07 11:41 ` Alan Cox
2002-08-07 23:08   ` Bill Davidsen
2002-08-08 10:49     ` Zwane Mwaikambo
2002-08-07 16:32 ` Thunder from the hill
2002-08-06 10:28 Petr Vandrovec
2002-08-01  6:38 Linux v2.4.19-rc5 Marcelo Tosatti
2002-08-02  1:47 ` [PATCH] pdc20265 problem Nick Orlov
2002-08-02  2:29   ` Nick Orlov
2002-08-02 12:27   ` Alan Cox
2002-08-02 12:52     ` Nick Orlov
2002-08-02 14:00       ` Bartlomiej Zolnierkiewicz
2002-08-02 14:45         ` Nick Orlov

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=3D5364C2.9030106@evision.ag \
    --to=dalecki@evision.ag \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@dalecki.de \
    /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