Upstreaming - how to deal with vendor fork

--===============0775800170486767223==
Content-Type: multipart/alternative; boundary="0000000000008a2d840650995124"

--0000000000008a2d840650995124
Content-Type: text/plain; charset="UTF-8"

Hi
Some time ago I managed to upstream one bugfix, now I have more changes but
I'm wondering how to approach this.

Suppose that I have found a bug and prepared a fix. However, the bug and
its solution has been found and tested on a custom board that is equipped
with a particular buggy device. The problem is that I cannot simply use
mainline/maintainer tree, build it, and run on my board as these source
trees do not have support for my board, as I use SoC vendor fork (v6.12)
supplied with their bsp with patches that add support for my board.

It's not mine decision - obviously - me and my team would be very willing
to use mainline but it would require some effort, time and obviously we
would not get vendor support in case of some bugs (it happened mamy times).

I can of course take the minimal set of patches for out board and apply
them over mainline but e.g. now I have a bugfix for mainline driver...but
in order to fully test it I need vendor changes as they did not upstream it
yet.

So at the end in order to test a bugfix on the mainline I would need to
apply patches that add support for my board as well patches from vendor
fork that add support for the rest of the functionality (not yet upstreamed
by vendor) that I need in order to test the bugfix.

Any sugestion on how to approach this? I have already few changes that
could be applied to mainline but due to what I described above they're just
waiting...

Will be grateful for some sugestion.

Best regards
Patryk

--0000000000008a2d840650995124
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Hi<div dir=3D"auto">Some time ago I managed to upstream o=
ne bugfix, now I have more changes but I&#39;m wondering how to approach th=
is.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Suppose that I have =
found a bug and prepared a fix. However, the bug and its solution has been =
found and tested on a custom board that is equipped with a particular buggy=
 device. The problem is that I cannot simply use mainline/maintainer tree, =
build it, and run on my board as these source trees do not have support for=
 my board, as I use SoC vendor fork (v6.12) supplied with their bsp with pa=
tches that add support for my board.</div><div dir=3D"auto"><br></div><div =
dir=3D"auto">It&#39;s not mine decision - obviously - me and my team would =
be very willing to use mainline but it would require some effort, time and =
obviously we would not get vendor support in case of some bugs (it happened=
 mamy times).</div><div dir=3D"auto"><br></div><div dir=3D"auto">I can of c=
ourse take the minimal set of patches for out board and apply them over mai=
nline but e.g. now I have a bugfix for mainline driver...but in order to fu=
lly test it I need vendor changes as they did not upstream it yet.</div><di=
v dir=3D"auto"><br></div><div dir=3D"auto">So at the end in order to test a=
 bugfix on the mainline I would need to apply patches that add support for =
my board as well patches from vendor fork that add support for the rest of =
the functionality (not yet upstreamed by vendor) that I need in order to te=
st the bugfix.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Any suges=
tion on how to approach this? I have already few changes that could be appl=
ied to mainline but due to what I described above they&#39;re just waiting.=
..</div><div dir=3D"auto"><br></div><div dir=3D"auto">Will be grateful for =
some sugestion.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Best reg=
ards=C2=A0</div><div dir=3D"auto">Patryk</div><div dir=3D"auto"><br></div><=
div dir=3D"auto"><br></div></div>

--0000000000008a2d840650995124--


--===============0775800170486767223==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kernelnewbies mailing list
[email protected]
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

--===============0775800170486767223==--