From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Hardik Prakash <hardikprakash.official@gmail.com>
Cc: linux-i2c@vger.kernel.org, linux-gpio@vger.kernel.org,
wsa@kernel.org, mario.limonciello@amd.com, brgl@bgdev.pl,
basavaraj.natikar@amd.com, linus.walleij@linaro.org
Subject: Re: [PATCH v3 0/1] i2c: designware: fix probe ordering for AMD GPIO on Lenovo Yoga 7 14AGP11
Date: Mon, 18 May 2026 10:06:31 +0300 [thread overview]
Message-ID: <agq6d6W-o-U6hoJl@ashevche-desk.local> (raw)
In-Reply-To: <CANTFpSWMjz-V_oOsP+7Ww57vhdDVwq0nJ0icQnp3qSq7-=yFRQ@mail.gmail.com>
On Sun, May 17, 2026 at 10:38:57PM +0530, Hardik Prakash wrote:
> On Sat, May 17, 2026 at 15:21, Andy Shevchenko wrote:
> > On Fri, May 15, 2026 at 09:45:15PM +0530, Hardik Prakash wrote:
> > > v3:
> > > - Patch 2 only (patch 1 already in Linus Walleij's tree)
> >
> > The patch numbering is broken. Where did 2/2 come from?
>
> Both patches are committed in my local tree. git format-patch counted
> both commits and numbered this 2/2. I excluded the 0001 file from the
> git send-email call since patch 1 is already in Linus Walleij's tree,
> but the numbering carried over from the two-commit series.
Don't do like this. New version should use proper --base and hence be only
1 patch. We do not confuse people by ghost patches.
> Apologies for the confusion. If preferred I can resend with 1/1
> numbering by dropping patch 1 from my local branch before running
> format-patch.
Make sure you base your tree on the official Linus Walleij's one, this will be
depicted in the cover letter when you supply proper --base to git-format-patch.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-05-18 7:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 16:15 [PATCH v3 0/1] i2c: designware: fix probe ordering for AMD GPIO on Lenovo Yoga 7 14AGP11 Hardik Prakash
2026-05-15 16:15 ` [PATCH v3 2/2] " Hardik Prakash
2026-05-15 17:34 ` [PATCH v3 0/1] " Mario Limonciello
2026-05-16 1:27 ` Hardik Prakash
2026-05-17 9:51 ` Andy Shevchenko
2026-05-17 17:08 ` Hardik Prakash
2026-05-18 7:06 ` Andy Shevchenko [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=agq6d6W-o-U6hoJl@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=basavaraj.natikar@amd.com \
--cc=brgl@bgdev.pl \
--cc=hardikprakash.official@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=wsa@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