From: Finn Thain <fthain@linux-m68k.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: lizhe <sensor1010@163.com>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] nubus: Remove redunant driver match function
Date: Mon, 20 Mar 2023 14:49:41 +1100 (AEDT) [thread overview]
Message-ID: <04bd0e13-d866-22f4-2b7a-200a31722a46@linux-m68k.org> (raw)
In-Reply-To: <20230319142058.cfu3ftjfaut3pqzt@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
On Sun, 19 Mar 2023, Uwe Kleine-König wrote:
> On Sun, Mar 19, 2023 at 07:01:33PM +0800, lizhe wrote:
>
> > u.kleline-koenig, please
> > delete the path you submitted, this patch does not belong to you
>
> Even if I'd agree, I couldn't. That's up to Finn (I think) to drop this
> patch again from his queue and then accept a similar patch from you.
I leave it up to Geert to apply Nubus patches that pass review. There is
no git tree for this subsystem and the only arch to make use of it so far
is m68k.
In my opinion, there's nothing novel about deleting code so it's quite
meaningless what "git log" says about authorship. That's doubly true for
redundant code, which compilers elide as a matter of course.
If some developers are receiving incentives to do juanitorial work (like
running coccinelle scripts) then I'd like to know whether a line added has
the same price as a line deleted.
Maybe some developers are deleting redundant code I wrote so as to make my
life easier as the maintainer. Maybe they are not getting paid for that.
I'm not aware of that having happened here, but if it did, thanks a lot.
next prev parent reply other threads:[~2023-03-20 3:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 4:08 [PATCH v1] nubus: Remove redunant driver match function Lizhe
2023-03-19 8:34 ` Finn Thain
[not found] ` <4cd5783e.1665.186f9882231.Coremail.sensor1010@163.com>
2023-03-19 14:20 ` Uwe Kleine-König
2023-03-20 3:49 ` Finn Thain [this message]
2023-03-20 9:40 ` Uwe Kleine-König
[not found] ` <74decde9.155d.186f9737c21.Coremail.sensor1010@163.com>
2023-03-20 3:48 ` Finn Thain
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=04bd0e13-d866-22f4-2b7a-200a31722a46@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=sensor1010@163.com \
--cc=u.kleine-koenig@pengutronix.de \
/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