[OpenWrt-Devel] [PATCH 4/4] ipq40xx: add support for secondary cores bringup

Павел be.dissent at gmail.com
Wed May 15 12:42:34 PDT 2019


ср, 15 мая 2019 г., 22:35 Petr Štetiar <ynezz at true.cz>:

> Павел <be.dissent at gmail.com> [2019-05-15 22:14:41]:
>
> > Not a problem, actually, but I've been suggested to squash them :)
> > https://github.com/openwrt/openwrt/pull/2043#issuecomment-491581897
>
> ok, thanks for the background, but still, squashing doesn't mean changing
> authorship and Christian has probably also warned you beforehand :-)
>
> "(Note: In some of the patches the "Author" in the commits is dissent1! So
>   watch out before sending them off)"
>

That was about different - I didn't switch from nickname to real name by
mistake when exported patches from my staging tree.

Thanks anyway, I'll add 2 commit messages into patchnotes within the
squashed patch. Is that okay?


> > Shouldn't the dev send the patch directly to me in order to be able to
> post
> > it on his behalf, like openwrt submitting patches guideline describes?
>
> From the kernel docs[1]:
>
> "The contribution is based upon previous work that, to the best of my
>  knowledge, is covered under an appropriate open source license and I have
> the
>  right under that license to submit that work with modifications, whether
>  created in whole or in part by me, under the same open source license
> (unless
>  I am permitted to submit under a different license), as indicated in the
> file;"
>
> so in short, kernel is covered by GPLv2 which allows you to do this if you
> retain the authorship.
>
> 1.
> https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin


Okay, thanks for pointing out.


>
> -- ynezz
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20190515/18d34997/attachment.html>


More information about the openwrt-devel mailing list