From: Jani Nikula <jani.nikula@linux.intel.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Ran Sun <sunran001@208suo.com>,
alexander.deucher@amd.com, airlied@gmail.com, daniel@ffwll.ch
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/amd/pm: Clean up errors in smu73_discrete.h
Date: Wed, 02 Aug 2023 13:09:35 +0300 [thread overview]
Message-ID: <87o7jpvjq8.fsf@intel.com> (raw)
In-Reply-To: <2f4f53e2-b12b-c77c-e7cb-8c0436a209e5@gmail.com>
On Wed, 02 Aug 2023, Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> On 01/08/2023 18:34, Jani Nikula wrote:
>> On Tue, 01 Aug 2023, Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>>> And it is unfortunate that you and @208suo.com people doesn't reply to
>>> review comments (try searching lore.kernel.org)
>>
>> Essentially a one-way firehose of patches pointed at our general
>> direction is not benefitial to the community. It's not participation,
>> it's not co-operation. If the review gets ignored, why should we invest
>> our time on *any* of the patches?
>>
>>
>
> Well, I guess this is the kind of "hey, some new orgs spam us tens
> of trivial patches, then we review them as usual, but people from
> that org are deaf in regards of our reviews (maybe deliberately?)".
> The exact same situation happened last year with @cdjrlc.com
> people, when they were notoriously known for spell-fixing and
> redundant word fixing patches. Many of these patches were correct,
> but some of them were not, triggering reviews requesting changes.
> Yet, they also ignore the reviews.
Since these emails, there have been 50+ more individual patches. :(
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2023-08-02 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 10:00 [PATCH] drm/amd/pm: Clean up errors in smu73_discrete.h Ran Sun
2023-08-01 11:16 ` Bagas Sanjaya
2023-08-01 11:34 ` Jani Nikula
2023-08-02 1:06 ` Bagas Sanjaya
2023-08-02 10:09 ` Jani Nikula [this message]
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=87o7jpvjq8.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bagasdotme@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sunran001@208suo.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