dev_info attachs the message to the device. And, the max compression
streams value, that triggers error, is added to the message.
---
 drivers/block/zram/zram_drv.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
index fb655e8..bb284db 100644
--- a/drivers/block/zram/zram_drv.c
+++ b/drivers/block/zram/zram_drv.c
@@ -333,7 +333,8 @@ static ssize_t max_comp_streams_store(struct device *dev,
        down_write(&zram->init_lock);
        if (init_done(zram)) {
                if (!zcomp_set_max_streams(zram->comp, num)) {
-                       pr_info("Cannot change max compression streams\n");
+                       dev_info(dev, "Cannot change max compression streams to 
%d\n",
+                               num);
                        ret = -EINVAL;
                        goto out;
                }
-- 
1.9.1

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

Reply via email to