From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Murthy, Arun R" <arun.r.murthy@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "Srikanth V, NagaVenkata" <nagavenkata.srikanth.v@intel.com>
Subject: RE: [PATCH 1/3] drm/i915/dp: use fsleep instead of usleep_rage for LT
Date: Mon, 23 Sep 2024 13:32:17 +0300 [thread overview]
Message-ID: <87r09a64pa.fsf@intel.com> (raw)
In-Reply-To: <IA0PR11MB7307B5BFFE772AC749C86AA7BA642@IA0PR11MB7307.namprd11.prod.outlook.com>
On Thu, 12 Sep 2024, "Murthy, Arun R" <arun.r.murthy@intel.com> wrote:
>> -----Original Message-----
>> From: Jani Nikula <jani.nikula@linux.intel.com>
>> Sent: Thursday, September 12, 2024 2:36 PM
>> To: Murthy, Arun R <arun.r.murthy@intel.com>; intel-xe@lists.freedesktop.org;
>> intel-gfx@lists.freedesktop.org
>> Cc: Murthy, Arun R <arun.r.murthy@intel.com>; Srikanth V, NagaVenkata
>> <nagavenkata.srikanth.v@intel.com>
>> Subject: Re: [PATCH 1/3] drm/i915/dp: use fsleep instead of usleep_rage for LT
>>
>> On Thu, 12 Sep 2024, Arun R Murthy <arun.r.murthy@intel.com> wrote:
>> > Aux RD Interval value depends on the value read from the dpcd register
>> > which is updated from the sink device use flseep thereby we adhere to
>> > the Documentation/timers/timers-howto.rst
>> >
>> > Signed-off-by: Srikanth V NagaVenkata
>> > <nagavenkata.srikanth.v@intel.com>
>> > Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
>>
>> Why do all the patches have two Signed-off-by's?
>>
> Findings are from Srikanth so giving credits to him as well.
Contrary to popular belief, Signed-off-by: actually has very little to
do with credits and authorship, and everything to do with certifying
that the work can be submitted and merged to the kernel [1].
What you're looking for is Co-developed-by: [2] in combination with
S-o-b.
BR,
Jani.
[1] https://docs.kernel.org/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin
[2] https://docs.kernel.org/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-09-23 10:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 5:05 [PATCH 0/3] Some correction in the DP Link Training dequence Arun R Murthy
2024-09-12 5:05 ` [PATCH 1/3] drm/i915/dp: use fsleep instead of usleep_rage for LT Arun R Murthy
2024-09-12 9:01 ` Jani Nikula
2024-09-12 10:04 ` Murthy, Arun R
2024-09-12 12:01 ` Srikanth V, NagaVenkata
2024-09-23 10:23 ` Jani Nikula
2024-09-12 9:05 ` Jani Nikula
2024-09-12 10:57 ` Murthy, Arun R
2024-09-23 10:32 ` Jani Nikula [this message]
2024-09-23 10:24 ` Jani Nikula
2024-09-23 12:59 ` Francois Dugast
2024-09-23 13:51 ` Jani Nikula
2024-09-12 5:05 ` [PATCH 2/3] drm/i915/dp: read Aux RD interval after reading the FFE preset Arun R Murthy
2024-09-12 9:04 ` Jani Nikula
2024-09-12 10:54 ` Murthy, Arun R
2024-09-12 11:58 ` Srikanth V, NagaVenkata
2024-09-23 6:21 ` Kandpal, Suraj
2024-09-23 6:28 ` Srikanth V, NagaVenkata
2024-09-23 6:32 ` Kandpal, Suraj
2024-09-23 6:56 ` Kandpal, Suraj
2024-09-24 5:58 ` Murthy, Arun R
2024-09-23 11:09 ` Jani Nikula
2024-09-24 6:00 ` Murthy, Arun R
2024-09-12 5:05 ` [PATCH 3/3] drm/i915/dp: Include the time taken by AUX Tx for timeout Arun R Murthy
2024-09-23 6:23 ` Kandpal, Suraj
2024-09-23 6:31 ` Srikanth V, NagaVenkata
2024-09-23 6:58 ` Kandpal, Suraj
2024-09-23 11:45 ` Jani Nikula
2024-09-12 6:12 ` ✓ Fi.CI.BAT: success for Some correction in the DP Link Training dequence Patchwork
2024-09-13 0:00 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-09-23 6:26 ` [PATCH 0/3] " Kandpal, Suraj
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=87r09a64pa.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=nagavenkata.srikanth.v@intel.com \
/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