devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Rob Herring <robh@kernel.org>,
	devicetree@vger.kernel.org, jernej.skrabec@siol.net,
	narmstrong@baylibre.com, airlied@linux.ie, jonas@kwiboo.se,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	a.hajda@samsung.com, robh+dt@kernel.org,
	Laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH] dt-bindings: display: bridge: tc358768: Remove maintainer information
Date: Thu, 17 Dec 2020 18:25:56 +0100	[thread overview]
Message-ID: <20201217172556.GA1339623@ravnborg.org> (raw)
In-Reply-To: <90d45716-4f4e-7379-07fd-74eff793e498@ti.com>

Hi Peter.

On Wed, Dec 16, 2020 at 09:44:59AM +0200, Peter Ujfalusi wrote:
> 
> On 15/12/2020 16.26, Rob Herring wrote:
> > On Tue, 15 Dec 2020 14:42:27 +0200, Peter Ujfalusi wrote:
> >> My employment with TI is coming to an end and I will not have access to
> >> the board where this bridge is connected to.
> >>
> >> It is better to remove a soon bouncing email address.
> >>
> >> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> >> ---
> >>  .../devicetree/bindings/display/bridge/toshiba,tc358768.yaml   | 3 ---
> >>  1 file changed, 3 deletions(-)
> >>
> > 
> > My bot found errors running 'make dt_binding_check' on your patch:
> > 
> > yamllint warnings/errors:
> > 
> > dtschema/dtc warnings/errors:
> > /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/display/bridge/toshiba,tc358768.yaml: 'maintainers' is a required property
> > /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/display/bridge/toshiba,tc358768.yaml: ignoring, error in schema: 
> > warning: no schema found in file: ./Documentation/devicetree/bindings/display/bridge/toshiba,tc358768.yaml
> 
> Right, so it is not that easy to not been able to maintain this... :o
> 
> Who should be documented as maintainer?
> Andrzej, Neil, David or Daniel?

I have no problem being listed as maintainer despite my very limited
knowledge on the HW. So unless you end up volunteering then just
add me.

	Sam

  reply	other threads:[~2020-12-17 17:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-15 12:42 [PATCH] dt-bindings: display: bridge: tc358768: Remove maintainer information Peter Ujfalusi
2020-12-15 14:26 ` Rob Herring
2020-12-16  7:44   ` Peter Ujfalusi
2020-12-17 17:25     ` Sam Ravnborg [this message]
2020-12-18  8:02       ` Peter Ujfalusi

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=20201217172556.GA1339623@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=a.hajda@samsung.com \
    --cc=airlied@linux.ie \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@siol.net \
    --cc=jonas@kwiboo.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=narmstrong@baylibre.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@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).