public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Chen-Yu Tsai <wens@kernel.org>
Cc: Sebastian Fricke <sebastian.fricke@collabora.com>,
	linux-media@vger.kernel.org
Subject: Re: [GIT PULL FOR 6.7] Mediatek Vcodec: Codec profile and level setting
Date: Thu, 23 Nov 2023 19:31:33 +0100	[thread overview]
Message-ID: <20231123193133.5f7323bb@coco.lan> (raw)
In-Reply-To: <CAGb2v64+-DE0t0M0aVQ4tBnMgsmaP96AeAJDy4AWPc0icAKfng@mail.gmail.com>

Em Thu, 23 Nov 2023 18:38:38 +0800
Chen-Yu Tsai <wens@kernel.org> escreveu:

> On Thu, Nov 23, 2023 at 6:02 PM Mauro Carvalho Chehab
> <mchehab@kernel.org> wrote:
> >
> > Em Fri, 27 Oct 2023 10:50:58 +0200
> > Sebastian Fricke <sebastian.fricke@collabora.com> escreveu:
> >  
> > > Hey Mauro and Hans,
> > >
> > > first attempt at doing a PR, could you please check and pull this?
> > >
> > > The following changes since commit 19e67e01eb1e84f3529770d084b93f16a4894c42:
> > >
> > >    media: venus: Fix firmware path for resources (2023-10-23 12:24:53 +0200)
> > >
> > > are available in the Git repository at:
> > >
> > >    https://gitlab.collabora.com/sebastianfricke/linux tags/for-6.7-signed
> > >
> > > for you to fetch changes up to ccd08a80f5e1844819874b01c5ff61e18aa9e133:
> > >
> > >    media: mediatek: vcodec: Set the supported vp9 profile for each platform (2023-10-26 09:09:21 +0200)  
> >
> >
> > Checkpatch is producing some warnings here:
> >
> > WARNING:COMMIT_LOG_LONG_LINE: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
> > #32:
> > The following changes since commit 19e67e01eb1e84f3529770d084b93f16a4894c42:
> >
> > ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 19e67e01eb1e ("media: venus: Fix firmware path for resources")'
> > #32:
> > The following changes since commit 19e67e01eb1e84f3529770d084b93f16a4894c42:
> >
> > ERROR:NOT_UNIFIED_DIFF: Does not appear to be a unified-diff format patch
> >
> > Could you please double-check those?  
> 
> It seems like you ran checkpatch against this pull request email, not
> the patches to be pulled in?

True. The problem seems to be due to whatever tool Sebastian made this PR.

My scripts rely on the format produced by "git pull", being picky with
the URL there. In particular, on Sebastian's PR, the URL is:

   https://gitlab.collabora.com/sebastianfricke/linux tags/for-6.7-signed

(3 spaces before URL)

While git request-pull produces:

  https://gitlab.collabora.com/sebastianfricke/linux tags/for-6.7-signed

(2 spaces before URL)

Anyway, PR applied by Hans.

Regards,
Mauro

      reply	other threads:[~2023-11-23 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27  8:50 [GIT PULL FOR 6.7] Mediatek Vcodec: Codec profile and level setting Sebastian Fricke
2023-10-27  9:23 ` [GIT PULL FOR 6.7] Mediatek Vcodec: Codec profile and level setting (#96306) Jenkins
2023-11-23 10:02 ` [GIT PULL FOR 6.7] Mediatek Vcodec: Codec profile and level setting Mauro Carvalho Chehab
2023-11-23 10:38   ` Chen-Yu Tsai
2023-11-23 18:31     ` Mauro Carvalho Chehab [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=20231123193133.5f7323bb@coco.lan \
    --to=mchehab@kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=sebastian.fricke@collabora.com \
    --cc=wens@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