On Tue, Sep 11, 2012 at 5:41 AM, James Bottomley <jbottomley@xxxxxxxxxxxxx> wrote: > On Tue, 2012-09-11 at 12:29 +0000, Dorau, Lukasz wrote: >> Hi James >> >> What are you going to do with the following four ISCI patches from isci-for-3.6 tag?: >> >> 6734092e66011def7875bd67beef889d0fee1cc9 isci: add a couple __iomem annotations >> 67787c330762eb884bf8c169fe942263d55ec162 isci: make function declaration match implementation >> a90037560588e51b3e98b49537799137cbfda17d isci: fix COMSAS negation timout workaround for WD SAS drives >> 6d70a74ffd616073a68ae0974d98819bfa8e6da6 isci: fix isci_pci_probe() generates warning on efi failure path >> (by: Dan Carpenter, Dave Maurer and Dan Williams) >> >> We hope they will get to the upstream kernel soon... > > They were tagged for -next and managed to miss the merge window because > it closed early. Just a one-off growing pain of the new process: http://marc.info/?l=linux-scsi&m=134327946218188&w=2 > I can't really do anything with them since they're > part of a signed pull, unless someone takes the tree apart and redoes > them as individual patches. > > None of them looks like -rc candidates, though because they don't seem > to have user visible bugs. They merge fine with latest upstream, do they need to be rebased as patches? -- Dan -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
