From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>
Subject: Re: linux-next: Fixes tag needs some work in the v4l-dvb tree
Date: Wed, 29 May 2019 18:11:04 -0300 [thread overview]
Message-ID: <20190529181104.6ae7e5de@coco.lan> (raw)
In-Reply-To: <20190529210511.GM1651@bigcity.dyn.berto.se>
Em Wed, 29 May 2019 23:05:11 +0200
"Niklas Söderlund" <niklas.soderlund@ragnatech.se> escreveu:
> Hi Stephen, Mauro,
>
> On 2019-05-29 08:04:54 +1000, Stephen Rothwell wrote:
> > Hi Mauro,
> >
> > In commit
> >
> > 0c310868826e ("media: rcar-csi2: Fix coccinelle warning for PTR_ERR_OR_ZERO()")
> >
> > Fixes tag
> >
> > Fixes: 3ae854cafd76 ("rcar-csi2: Use standby mode instead of resetting")
> >
> > has these problem(s):
> >
> > - Target SHA1 does not exist
> >
> > Did you mean
> >
> > Fixes: d245a940d97b ("media: rcar-csi2: Use standby mode instead of resetting")
>
> Yes I meant d245a940d97b commit, for some reason I was on the wrong
> branch when looking up the sha1 for the fixes tag and used one from a
> local development branch.
>
> This is my mess, sorry about that. What can I do to help fix it?
That's a good question... no idea. Rebasing the tree due to that sounds
a bad idea. Reverting/reapplying also doesn't sound the best thing,
as it will just make -stable people even more confused.
I should probably try to implement a script like the one Stephen
has on my patch import scripts.
Thanks,
Mauro
next prev parent reply other threads:[~2019-05-29 21:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 22:04 linux-next: Fixes tag needs some work in the v4l-dvb tree Stephen Rothwell
2019-05-29 21:05 ` Niklas Söderlund
2019-05-29 21:11 ` Mauro Carvalho Chehab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-17 22:29 Stephen Rothwell
2022-07-17 22:25 Stephen Rothwell
2021-03-22 20:58 Stephen Rothwell
2020-11-17 8:04 Stephen Rothwell
2020-07-04 20:13 Stephen Rothwell
2020-05-20 11:52 Stephen Rothwell
2020-05-18 22:10 Stephen Rothwell
2020-02-27 21:06 Stephen Rothwell
2020-01-08 20:31 Stephen Rothwell
2019-10-10 20:47 Stephen Rothwell
2019-10-11 12:28 ` Benoit Parrot
2019-06-22 13:47 Stephen Rothwell
2019-04-22 21:22 Stephen Rothwell
2019-01-16 21:02 Stephen Rothwell
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=20190529181104.6ae7e5de@coco.lan \
--to=mchehab@kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=sfr@canb.auug.org.au \
/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).