From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Tsuchiya Yuto <kitakar@gmail.com>,
Andy Shevchenko <andy@kernel.org>,
Yury Luneff <yury.lunev@gmail.com>,
Nable <nable.maininbox@googlemail.com>,
"andrey.i.trufanov" <andrey.i.trufanov@gmail.com>,
Fabio Aiuto <fabioaiuto83@gmail.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
linux-staging@lists.linux.dev
Subject: Re: [PATCH 1/3] media: atomisp: revert "don't pass a pointer to a local variable"
Date: Mon, 13 Jun 2022 18:39:19 +0300 [thread overview]
Message-ID: <YqdaJ6fzEzeWpIGz@smile.fi.intel.com> (raw)
In-Reply-To: <20220613145820.GF2146@kadam>
On Mon, Jun 13, 2022 at 05:58:20PM +0300, Dan Carpenter wrote:
> On Sun, Jun 12, 2022 at 09:22:55PM +0200, Andy Shevchenko wrote:
> > > Note there is another patch in this series, which fixes the warning
> > > in another way.
> >
> > > Fixes: fa1451374ebf ("media: atomisp: don't pass a pointer to a local variable")
> >
> > Dunno for media subsystem, but for ones that Greg is maintain, the
> > point is that revert itself is already kinda fix and no need to have a
> > Fixes tag, instead the commit message should clearly have the
> > automatically generated line of revert (with the rest of the
> > explanation why that is needed). Just sharing my experience.
>
> How would that work in this case? We don't have a reference to the git
> hash.
What do you mean? `git revert` adds the hash of the commit being reverted.
> The `git revert` command came from early days of git and I always
> feel like it hasn't keep up with how git is used these days. The
> subject doesn't have the subsystem prefix. The commit message is wrong.
> It uses the full git hash instead of the 12 char hash. It doesn't have
> a fixes tag. Hans's commit is only correct because he re-wrote
> basically everything.
>
> Do a `git --grep=revert`. Some of them you can grep for "This reverts
> commit 8bdc2a190105e862dfe7a4033f2fd385b7e58ae8." but there are a lot
> which are not machine parsable
Why not? The format of the string hasn't been changed, no difference from other
patterns.
P.S. I have told this as my experience and what Greg told me, feel free to
discuss with him or others, I'm pretty much okay if Hans' patch goes as is.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-06-13 15:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 16:05 [PATCH 0/3] media: atomisp: fix "don't pass a pointer to a local variable" Hans de Goede
2022-06-12 16:05 ` [PATCH 1/3] media: atomisp: revert " Hans de Goede
2022-06-12 19:22 ` Andy Shevchenko
2022-06-13 14:58 ` Dan Carpenter
2022-06-13 15:39 ` Andy Shevchenko [this message]
2022-06-14 7:19 ` Dan Carpenter
2022-06-12 16:05 ` [PATCH 2/3] media: atomisp: fix uninitialized stack mem usage in ia_css_rmgr_acq_vbuf() Hans de Goede
2022-06-12 16:05 ` [PATCH 3/3] media: atomisp: fix -Wdangling-pointer warning Hans de Goede
2022-06-12 19:29 ` [PATCH 0/3] media: atomisp: fix "don't pass a pointer to a local variable" Andy Shevchenko
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=YqdaJ6fzEzeWpIGz@smile.fi.intel.com \
--to=andy.shevchenko@gmail.com \
--cc=andrey.i.trufanov@gmail.com \
--cc=andy@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=fabioaiuto83@gmail.com \
--cc=hdegoede@redhat.com \
--cc=kitakar@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=nable.maininbox@googlemail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=yury.lunev@gmail.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