The patch titled ADT746X: logical-bitwise & confusion in set_max_duty_at_crit() has been removed from the -mm tree. Its filename was adt746x-logical-bitwise-confusion-in-set_max_duty_at_crit.patch This patch was dropped because it was nacked The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: ADT746X: logical-bitwise & confusion in set_max_duty_at_crit() From: Roel Kluin <12o3l@xxxxxxxxxx> logical-bitwise & confusion Signed-off-by: Roel Kluin <12o3l@xxxxxxxxxx> Cc: Mark M. Hoffman <mhoffman@xxxxxxxxxxxxx> Acked-by: Colin Leroy <colin@xxxxxxxxxx> Cc: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx> Cc: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx> Acked-by: "Darrick J. Wong" <djwong@xxxxxxxxxx> Cc: Jean Delvare <khali@xxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/hwmon/adt7473.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff -puN drivers/hwmon/adt7473.c~adt746x-logical-bitwise-confusion-in-set_max_duty_at_crit drivers/hwmon/adt7473.c --- a/drivers/hwmon/adt7473.c~adt746x-logical-bitwise-confusion-in-set_max_duty_at_crit +++ a/drivers/hwmon/adt7473.c @@ -565,11 +565,11 @@ static ssize_t set_max_duty_at_crit(stru const char *buf, size_t count) { - u8 reg; + u8 reg, temp; struct i2c_client *client = to_i2c_client(dev); struct adt7473_data *data = i2c_get_clientdata(client); - int temp = simple_strtol(buf, NULL, 10); - temp = temp && 0xFF; + + temp = simple_strtol(buf, NULL, 10); mutex_lock(&data->lock); data->max_duty_at_overheat = temp; _ Patches currently in -mm which might be from 12o3l@xxxxxxxxxx are linux-next.patch adt746x-logical-bitwise-confusion-in-set_max_duty_at_crit.patch block-blk-mergec-inverted-likeliness-in-ll_back_merge_fn.patch spi_mpc83xx-much-improved-driver.patch likeliness-accounting-change-and-cleanup.patch likely_prof-update-to-test_and_set_bit_lock-clear_bit_unlock.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html