linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
Cc: Lucas Stach <l.stach@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	Laurentiu Palcu <laurentiu.palcu@nxp.com>,
	dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, agx@sigxcpu.org, lukas@mntmn.com
Subject: Re: [PATCH v9 0/5] Add support for iMX8MQ Display Controller Subsystem
Date: Sat, 29 Aug 2020 09:25:49 +0200	[thread overview]
Message-ID: <20200829072549.GA729648@ravnborg.org> (raw)
In-Reply-To: <20200828083620.6m5yhcv7rg5tckzh@fsr-ub1864-141>

Hi Laurentiu.

> As to who is going to do the actual merge, I know we had a brief
> discussion about it some time ago and I was supposed to apply for
> drm-misc rights, however it feels a little awkward to merge my own
> code... :)

You are encouraged to commit your own code, it is anyway you who knows
the state of the code best. The golden rule is that the code must have
been seen by somone else before you merge, are translated there must be
an acked-by or reviewed-by on each of the patches.

If you look at ths page:

    https://people.freedesktop.org/~seanpaul/whomisc.html

You can see that a lot of people commit their own code in drm-misc.
Example:

    Daniel Vetter <daniel.vetter@ffwll.ch>, <daniel@ffwll.ch>
    (authored=159 committed=249 self_committed=153)

There is only a few patches written by Daniel that is committed by
someone else. And all patches committed by Daniel carries an
a-b or -rb by someone else.

> Though, I might not even qualify for drm-misc rights anyway,
> considering I haven't been very active in this area... :/
> 
> On that note, I will probably need help with the merging, provided it's
> still happenning. Will you be able to help me out with this?

If the challenge is only to push the patches to drm-misc-next there
is a lot of people that can help you. I would be happy to do so, but
would need a resend as I have deleted the patches from my inbox.

I could dig the pathces out somewhere else, but a fresh rebase would
be preferred.

	Sam

  reply	other threads:[~2020-08-29  7:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-31  8:18 [PATCH v9 0/5] Add support for iMX8MQ Display Controller Subsystem Laurentiu Palcu
2020-07-31  8:18 ` [PATCH v9 1/5] drm/imx: compile imx directory by default Laurentiu Palcu
2020-07-31  8:46   ` Guido Günther
2020-07-31  8:18 ` [PATCH v9 2/5] drm/imx: Add initial support for DCSS on iMX8MQ Laurentiu Palcu
2020-07-31  8:56   ` Guido Günther
2020-07-31  8:18 ` [PATCH v9 3/5] drm/imx/dcss: use drm_bridge_connector API Laurentiu Palcu
2020-07-31  8:18 ` [PATCH v9 4/5] MAINTAINERS: Add entry for i.MX 8MQ DCSS driver Laurentiu Palcu
2020-07-31  8:48   ` Guido Günther
2020-07-31  8:18 ` [PATCH v9 5/5] dt-bindings: display: imx: add bindings for DCSS Laurentiu Palcu
2020-07-31  8:52   ` Guido Günther
2020-07-31 19:34   ` Rob Herring
2020-07-31  8:54 ` [PATCH v9 0/5] Add support for iMX8MQ Display Controller Subsystem Guido Günther
2020-09-05 11:49   ` Guido Günther
2020-08-28  8:36 ` Laurentiu Palcu
2020-08-29  7:25   ` Sam Ravnborg [this message]
2020-08-31 10:37   ` Lucas Stach
2020-08-31 11:24     ` Laurentiu Palcu
2020-09-09 15:02       ` Lucas Stach
2020-09-10  6:47         ` Daniel Vetter
2020-09-10  8:04           ` Laurentiu Palcu
2020-09-10 18:41             ` Sam Ravnborg

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=20200829072549.GA729648@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=agx@sigxcpu.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=l.stach@pengutronix.de \
    --cc=laurentiu.palcu@nxp.com \
    --cc=laurentiu.palcu@oss.nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas@mntmn.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;
as well as URLs for NNTP newsgroup(s).