Re: 2.6.20-rc1-mm1

From: Bartlomiej Zolnierkiewicz
Date: Mon Dec 18 2006 - 15:06:29 EST


On 12/15/06, Andrew Morton <akpm@xxxxxxxx> wrote:

+toshiba-tc86c001-ide-driver-take-2.patch

Acked-by: Bartlomiej Zolnierkiewicz <bzolnier@xxxxxxxxx>

IMO this can be merged for 2.6.20 as it is new driver
(which is clean, tested and acked by Alan already)

All 693 patches:

hpt3xx-rework-rate-filtering.patch
HPT3xx: rework rate filtering

ACK

hpt3xx-rework-rate-filtering-tidy.patch
hpt3xx-rework-rate-filtering-tidy

ACK

hpt3xx-print-the-real-chip-name-at-startup.patch
HPT3xx: print the real chip name at startup

ACK

hpt3xx-switch-to-using-pci_get_slot.patch
HPT3xx: switch to using pci_get_slot()

ACK

hpt3xx-cache-channels-mcr-address.patch
[PATCH] HPT3xx: cache channel's MCR address

ACK

hpt3x7-merge-speedproc-handlers.patch
HPT3x7: merge speedproc handlers

ACK

hpt370-clean-up-dma-timeout-handling.patch
HPT370: clean up DMA timeout handling

ACK

hpt3xx-init-code-rewrite.patch
HPT3xx: init code rewrite

ACK

piix-fix-82371mx-enablebits.patch
PIIX: fix 82371MX enablebits

ACK, thought I haven't compared wrt datasheet yet

piix-remove-check-for-broken-mw-dma-mode-0.patch
PIIX: remove check for broken MW DMA mode 0

ACK, 100% correct and non-intrusive cleanup

piix-slc90e66-pio-mode-fallback-fix.patch
PIIX/SLC90E66: PIO mode fallback fix

ACK, this is an important bugfix

pdc202xx_new-remove-useless-code.patch
pdc202xx_new: remove useless code

ACK, nice cleanup

pdc202xx_-remove-check_in_drive_lists-abomination.patch
pdc202xx_*: remove check_in_drive_lists() abomination

ACK, ditto

I think that all above patches from Sergei should be merged now as they
are either bugfixes or not-intrusive cleanups and got more than enough
exposure in -mm (since 2.6.17-mm).

jmicron-warning-fix.patch

Wouldn't it be neater to add BUG() instead? Seems to fix warning
for me and documents nicely that this case cannot happen.

Thanks,
Bart
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/