From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Kars de Jong <jongk@linux-m68k.org>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Boaz Harrosh <bharrosh@panasas.com>,
Christoph Hellwig <hch@infradead.org>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
"David S. Miller" <davem@davemloft.net>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 1/1] Remove of old NCR53C9x/esp family of drivers
Date: Thu, 31 Jan 2008 13:31:56 -0600 [thread overview]
Message-ID: <1201807916.3131.42.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0801311953540.22762@anakin>
On Thu, 2008-01-31 at 19:55 +0100, Geert Uytterhoeven wrote:
> On Thu, 31 Jan 2008, James Bottomley wrote:
> > On Mon, 2008-01-07 at 07:07 +0100, Kars de Jong wrote:
> > > On do, 2008-01-03 at 20:05 +0100, Geert Uytterhoeven wrote:
> > > > On Thu, 3 Jan 2008, James Bottomley wrote:
> > > > > On Thu, 2008-01-03 at 17:40 +0200, Boaz Harrosh wrote:
> > > > > > As recommended by Christoph Hellwig. There is no use
> > > > > > of Fixing these drivers, since there is a much simpler
> > > > > > and modern esp infrastructure with David Miller's esp_scsi
> > > > > >
> > > > > > - Remove all driver files dependent on NCR53C9x.c
> > > > > > deleted: drivers/scsi/NCR53C9x.c
> > > > > > deleted: drivers/scsi/NCR53C9x.h
> > > > > > deleted: drivers/scsi/blz1230.c
> > > > > > deleted: drivers/scsi/blz2060.c
> > > > > > deleted: drivers/scsi/cyberstorm.c
> > > > > > deleted: drivers/scsi/cyberstormII.c
> > > > > > deleted: drivers/scsi/dec_esp.c
> > > > > > deleted: drivers/scsi/fastlane.c
> > > > > > deleted: drivers/scsi/mac_esp.c
> > > > > > deleted: drivers/scsi/mca_53c9x.c
> > > > > > deleted: drivers/scsi/oktagon_esp.c
> > > > > > deleted: drivers/scsi/oktagon_io.S
> > > > > > deleted: drivers/scsi/sun3x_esp.c
> > > > > >
> > > > > > - Remove above list from drivers/scsi/Kconfig &&
> > > > > > drivers/scsi/Makefile
> > > > >
> > > > > OK, I'll split this into four pieces for scsi-pending, since there are
> > > > > three separate interest groups with signoffs to collect (MCA, m68k and
> > > > > alpha) plus the core removal.
> > > >
> > > > Anybody who can look into converting the m68k NCR53C9x drivers and has
> > > > hardware to test (some of) them? I don't think we can afford losing one
> > > > third of our SCSI drivers...
> > >
> > > I'll have a look at this. I can only test it on Blizzard 1260 hardware
> > > though.
> >
> > OK, time's up.
> >
> > These drivers are now unbuildable in mainline because of the promised
> > sg_table updates. They either get removed, fixed or marked as BROKEN.
> > Which is it to be?
>
> Is git smart enough to follow history between files that get removed and
> readded?
Yes. git revert on the removal changeset will re-add all the files and
try to put the entries back into Kconfig and Makefile.
> If yes, I think you can remove them.
> If no, please mark them as BROKEN.
OK ... I'll wave the magic wand.
James
next prev parent reply other threads:[~2008-01-31 19:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 15:17 [PATCH 0/1] Remove of old NCR53C9x/esp family of drivers Boaz Harrosh
2008-01-03 15:40 ` [PATCH 1/1] " Boaz Harrosh
2008-01-03 18:16 ` James Bottomley
2008-01-03 19:05 ` Geert Uytterhoeven
2008-01-03 19:19 ` James Bottomley
2008-01-03 19:46 ` Michael Schmitz
2008-01-03 23:02 ` David Miller
2008-01-04 9:59 ` Geert Uytterhoeven
2008-01-04 11:05 ` Finn Thain
2008-01-04 11:49 ` David Miller
2008-01-05 5:07 ` Finn Thain
2008-02-21 7:59 ` mac_esp and PIO, was " Finn Thain
2008-01-07 6:07 ` Kars de Jong
2008-01-31 18:08 ` James Bottomley
2008-01-31 18:55 ` Geert Uytterhoeven
2008-01-31 19:06 ` Boaz Harrosh
2008-01-31 19:31 ` James Bottomley [this message]
2008-02-08 6:04 ` Christoph Hellwig
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=1201807916.3131.42.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=bharrosh@panasas.com \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=jongk@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=macro@linux-mips.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.