Double commits in i2c/for-next branch?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Wolfram,

I noticed my patch was applied twice in the next branch
with different commit IDs.



[1] commit 6a62974b667f3976ec44e255bed31746cca1ff51
Author: Masahiro Yamada <yamada.masahiro@xxxxxxxxxxxxx>
Date:   Fri Oct 23 19:52:00 2015 +0900

    i2c: uniphier_f: add UniPhier FIFO-builtin I2C driver


[2] commit f496cf367b613c94e40893e07e1b20470deb9363
Author: Masahiro Yamada <yamada.masahiro@xxxxxxxxxxxxx>
Date:   Fri Oct 23 19:52:00 2015 +0900

    i2c: uniphier_f: add UniPhier FIFO-builtin I2C driver



Please let me confirm if I correctly understood
the branch strategy of this subsystem.



[1] was applied to i2c/for-4.4 and then merged
into i2c/for-next.   It is supposed to be pulled
into the mainline in this merge window.


[2] was directly applied to i2c/for-next and
won't be pulled into the mainline.  It will only
remain in linux-next.



Is this correct?





-- 
Best Regards
Masahiro Yamada
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux GPIO]     [Linux SPI]     [Linux Hardward Monitoring]     [LM Sensors]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux