From: Mark Brown <broonie@kernel•org>
To: Biju Das <biju.das.jz@bp•renesas.com>
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>,
Geert Uytterhoeven <geert+renesas@glider•be>
Subject: Re: linux-next: Fixes tag needs some work in the spi tree
Date: Fri, 18 Mar 2022 15:44:00 +0000 [thread overview]
Message-ID: <YjSowNPTqUHDbLKE@sirena.org.uk> (raw)
In-Reply-To: <OS0PR01MB5922ED18407C0728F09941A486139@OS0PR01MB5922.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 306 bytes --]
On Fri, Mar 18, 2022 at 07:10:59AM +0000, Biju Das wrote:
> Hi Stephen and Mark,
>
> My bad, I have added Fixes tag at last minute and missed running
> Check patch with that change.
>
> Is it possible to manually fix this?
No, that'd involve rebasing. It's fine, just remember this in future.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-03-18 15:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 21:18 linux-next: Fixes tag needs some work in the spi tree Stephen Rothwell
2022-03-18 7:10 ` Biju Das
2022-03-18 15:44 ` Mark Brown [this message]
2022-03-18 15:48 ` Biju Das
-- strict thread matches above, loose matches on Subject: below --
2026-01-13 21:37 Stephen Rothwell
2026-01-13 21:41 ` Stephen Rothwell
2024-02-19 21:44 Stephen Rothwell
2024-02-19 22:48 ` Randy Dunlap
2024-02-19 22:54 ` Mark Brown
2021-05-11 22:24 Stephen Rothwell
2021-04-11 22:37 Stephen Rothwell
2021-01-11 20:36 Stephen Rothwell
2021-01-11 20:58 ` Pratyush Yadav
2021-01-11 23:00 ` Mark Brown
2019-04-01 18:12 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=YjSowNPTqUHDbLKE@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=biju.das.jz@bp$(echo .)renesas.com \
--cc=geert+renesas@glider$(echo .)be \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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