The patch titled
     mmc: bfin_sdh: fix unused sg warning on BF51x/BF52x systems
has been removed from the -mm tree.  Its filename was
     mmc-bfin_sdh-fix-unused-sg-warning-on-bf51x-bf52x-systems.patch

This patch was dropped because it was merged into mainline or a subsystem tree

The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/

------------------------------------------------------
Subject: mmc: bfin_sdh: fix unused sg warning on BF51x/BF52x systems
From: Mike Frysinger <[email protected]>

The local sg variable is only used with BF54x code.

Signed-off-by: Mike Frysinger <[email protected]>
Cc: <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
---

 drivers/mmc/host/bfin_sdh.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff -puN 
drivers/mmc/host/bfin_sdh.c~mmc-bfin_sdh-fix-unused-sg-warning-on-bf51x-bf52x-systems
 drivers/mmc/host/bfin_sdh.c
--- 
a/drivers/mmc/host/bfin_sdh.c~mmc-bfin_sdh-fix-unused-sg-warning-on-bf51x-bf52x-systems
+++ a/drivers/mmc/host/bfin_sdh.c
@@ -115,7 +115,6 @@ static int sdh_setup_data(struct sdh_hos
        unsigned int length;
        unsigned int data_ctl;
        unsigned int dma_cfg;
-       struct scatterlist *sg;
 
        dev_dbg(mmc_dev(host->mmc), "%s enter flags: 0x%x\n", __func__, 
data->flags);
        host->data = data;
@@ -151,6 +150,7 @@ static int sdh_setup_data(struct sdh_hos
 #if defined(CONFIG_BF54x)
        dma_cfg |= DMAFLOW_ARRAY | NDSIZE_5 | RESTART | WDSIZE_32 | DMAEN;
        {
+               struct scatterlist *sg;
                int i;
                for_each_sg(data->sg, sg, host->dma_len, i) {
                        host->sg_cpu[i].start_addr = sg_dma_address(sg);
_

Patches currently in -mm which might be from [email protected] are

linux-next.patch
fbdev-bf54x-lq043fb-bfin-t350mcqb-fb-drop-custom-mmap-handler.patch
blackfin-remove-the-obsolete-and-unnecessary-dma-api-comments.patch

--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to