From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Jakub Kicinski <kuba@kernel.org>, Greg KH <gregkh@linuxfoundation.org>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Jeffrey Townsend <jeffrey.townsend@bigswitch.com>,
"David S . Miller" <davem@davemloft.net>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
John W Linville <linville@tuxdriver.com>
Subject: Re: [PATCH 2/2] ethernet: igb: e1000_phy: Check for ops.force_speed_duplex existence
Date: Tue, 5 Jan 2021 18:16:59 +0100 [thread overview]
Message-ID: <c1ad26c6-a4a6-d161-1b18-476b380f4e58@molgen.mpg.de> (raw)
In-Reply-To: <20201103103940.2ed27fa2@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
Dear Jakub, dear Greg,
Am 03.11.20 um 19:39 schrieb Jakub Kicinski:
> On Tue, 3 Nov 2020 08:35:09 +0100 Paul Menzel wrote:
>> According to *Developer's Certificate of Origin 1.1* [3], it’s my
>> understanding, that it is *not* required. The items (a), (b), and (c)
>> are connected by an *or*.
>>
>>> (b) 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; or
>
> Ack, but then you need to put yourself as the author, because it's
> you certifying that the code falls under (b).
>
> At least that's my understanding.
Greg, can you please clarify, if it’s fine, if I upstream a patch
authored by somebody else and distributed under the GPLv2? I put them as
the author and signed it off.
(In this case the change, adding an if condition, is also trivial.)
Kind regards,
Paul
next prev parent reply other threads:[~2021-01-05 17:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 23:13 [PATCH 0/2] Upstream ONL patch for PHY BCM5461S Paul Menzel
2020-11-02 23:13 ` [PATCH 1/2] ethernet: igb: Support " Paul Menzel
2020-11-02 23:24 ` Paul Menzel
2020-11-03 1:15 ` Florian Fainelli
2020-11-02 23:13 ` [PATCH 2/2] ethernet: igb: e1000_phy: Check for ops.force_speed_duplex existence Paul Menzel
2020-11-03 0:19 ` Jakub Kicinski
2020-11-03 7:35 ` Paul Menzel
2020-11-03 18:39 ` Jakub Kicinski
2021-01-05 17:16 ` Paul Menzel [this message]
2021-01-05 17:25 ` Greg KH
2021-01-19 6:55 ` Paul Menzel
2021-01-19 17:05 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c1ad26c6-a4a6-d161-1b18-476b380f4e58@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.townsend@bigswitch.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).