From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Dmitry Perchanov <dmitry.perchanov@intel.com>,
linux-media@vger.kernel.org,
Sakari Ailus <sakari.ailus@intel.com>
Subject: Re: [GIT PULL FOR v6.5] uvcvideo changes
Date: Fri, 9 Jun 2023 09:14:47 +0100 [thread overview]
Message-ID: <20230609091442.14e2bbcc@sal.lan> (raw)
In-Reply-To: <20230607175629.GK5058@pendragon.ideasonboard.com>
Em Wed, 7 Jun 2023 20:56:29 +0300
Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:
> On Wed, Jun 07, 2023 at 08:47:38PM +0300, Dmitry Perchanov wrote:
> > Hi Laurent,
> > I saw that Jenkins failed to apply this patch..
> >
> > > FAILED: patch patch patches/0002-media-uapi-v4l-Intel-metadata-format-update.patch doesn't apply:
> > > Applying patch patches/0002-media-uapi-v4l-Intel-metadata-format-update.patch
> > > can't find file to patch at input line 21
> >
> > ¯\_(O_o)_/¯
>
> I suspect Jenkins may be trying to apply the patch to the wrong branch.
Jenkins always try to apply patches on the top of media-stage master.
One of the issues with PR e-mails is that they don't specify on
what tree/branch a patch should be applied. Ok, it would be doable
to have some heuristics logic to try a couple of different options
and/or use "since commit" to identify if the tree is the correct
one, but the current logic lacks that.
The error message seems to indicate that the patch didn't apply
cleanly there. It should have been preserved the build information,
though.
Regards,
Mauro
next prev parent reply other threads:[~2023-06-09 8:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 18:30 [GIT PULL FOR v6.5] uvcvideo changes Laurent Pinchart
2023-06-05 18:55 ` [GIT PULL FOR v6.5] uvcvideo changes (#92342) Jenkins
2023-06-07 17:21 ` [GIT PULL FOR v6.5] uvcvideo changes Dmitry Perchanov
2023-06-07 17:27 ` Laurent Pinchart
2023-06-07 17:47 ` Dmitry Perchanov
2023-06-07 17:56 ` Laurent Pinchart
2023-06-09 8:14 ` Mauro Carvalho Chehab [this message]
2023-06-09 11:46 ` [GIT PULL FOR v6.5] uvcvideo changes (#92342) Jenkins
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=20230609091442.14e2bbcc@sal.lan \
--to=mchehab@kernel.org \
--cc=dmitry.perchanov@intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@intel.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