public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@kernel.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Minjie Du <duminjie@vivo.com>,
	linux-i2c@vger.kernel.org, kernel-janitors@vger.kernel.org,
	opensource.kernel@vivo.com, LKML <linux-kernel@vger.kernel.org>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: [v2] i2c: busses: fix parameter check in i2c_gpio_fault_injector_init()
Date: Wed, 12 Jul 2023 23:53:43 +0200	[thread overview]
Message-ID: <20230712215343.57yhhk5kajtsfaax@intel.intel> (raw)
In-Reply-To: <1e809b1e-16ec-3e2c-1ced-f50a78811131@web.de>

Hi Markus,

On Wed, Jul 12, 2023 at 08:30:11PM +0200, Markus Elfring wrote:
> > > v1-v2:
> > > Fix judge typo.
> >
> > Please next time add the changelog after the "---" section.
> >
> > You will also need:
> >
> > Fixes: 14911c6f48ec ("i2c: gpio: add fault injector")
> > Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>
> > Cc: <stable@vger.kernel.org> # v4.16+
> >
> > Said that:
> >
> > Reviewed-by: Andi Shyti <andi.shyti@kernel.org>
> 
> * How appropriate is your presentation of this tag “in advance”?
 
1. These are all things that can be fixed before pushing the
   patch. I Wouldn't feel like asking to resend for a Fixes tag
   and few minor adjustments in the commit log, because:

   1a. it's spam in the mailing list
   1b. it annoys the person who sent the fix and demotivates him
       to send more fixes

   but more important:

   1c. I learned that tools like b4 are able to take the Fixes:
       tag even afterwards. I had this same discussion just
       today[*].

2. This is quite a common practice in other communities. However,
   with Wolfram we agreed that I wouldn't r-b "in advance" after
   asking minor fixes in the patch (but not in the commit log).

> * Would you like to take another look at the properties for
>   the reviewer's statement of oversight?
> 
> See also:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.5-rc1#n542
> 
> 
> Would a subject like “[PATCH v3] i2c: gpio: Fix an error check in i2c_gpio_fault_injector_init()”
> be more appropriate?

Every community has its own rules. I met both the approaches,
that's why I wouldn't be so strict. I'm sure Minjie will be able
to fix those mistakes in the future.

Said that... Minjie, do you mind sending a v3 with the commit log
fixed and all the proper tags and make everyone happy? :)

Andi

[*] https://lore.kernel.org/all/32ca3740-901c-47f2-81ab-c51e8751eefe@sirena.org.uk/

      parent reply	other threads:[~2023-07-12 21:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12 11:22 [PATCH v2] i2c: busses: fix parameter check in i2c_gpio_fault_injector_init() Minjie Du
2023-07-12 15:02 ` Andi Shyti
     [not found]   ` <1e809b1e-16ec-3e2c-1ced-f50a78811131@web.de>
2023-07-12 21:53     ` Andi Shyti [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=20230712215343.57yhhk5kajtsfaax@intel.intel \
    --to=andi.shyti@kernel.org \
    --cc=Markus.Elfring@web.de \
    --cc=duminjie@vivo.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=opensource.kernel@vivo.com \
    --cc=wsa+renesas@sang-engineering.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