From: Vineet Gupta <vgupta@kernel.org>
To: Sergey Matyukevich <geomatsi@gmail.com>,
linux-snps-arc@lists.infradead.org
Cc: kbuild-all@lists.01.org, Vineet Gupta <vgupta@kernel.org>
Subject: Re: [vgupta-arc:for-next 3/4] arch/arc/kernel/disasm.c:494:23: error: 'struct pt_regs' has no member named 'gp'; did you mean 'fp'?
Date: Tue, 26 Apr 2022 21:04:15 -0700 [thread overview]
Message-ID: <f87e457e-72fe-7d39-5045-3c8d2271f638@kernel.org> (raw)
In-Reply-To: <Ymef0FkwCE/hdUtb@curiosity>
On 4/26/22 00:31, Sergey Matyukevich wrote:
> I have just sent a fixup for this snafu:
> https://lore.kernel.org/linux-snps-arc/20220426072447.125975-1-geomatsi@gmail.com/T/#u
>
> IIUC, you have not yet sent a pull-request for next release. So probably
> it makes sense to squash this commit with b08a66fb680018b6 ("ARC: disasm:
> handle ARCv2 case in kprobe get/set functions").
Yes this is merge-window stuff so will go in next cycle.
I've added a fixup and push for-next.
Thx,
-Vineet
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
WARNING: multiple messages have this Message-ID (diff)
From: Vineet Gupta <vgupta@kernel.org>
To: kbuild-all@lists.01.org
Subject: Re: [vgupta-arc:for-next 3/4] arch/arc/kernel/disasm.c:494:23: error: 'struct pt_regs' has no member named 'gp'; did you mean 'fp'?
Date: Tue, 26 Apr 2022 21:04:15 -0700 [thread overview]
Message-ID: <f87e457e-72fe-7d39-5045-3c8d2271f638@kernel.org> (raw)
In-Reply-To: <Ymef0FkwCE/hdUtb@curiosity>
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
On 4/26/22 00:31, Sergey Matyukevich wrote:
> I have just sent a fixup for this snafu:
> https://lore.kernel.org/linux-snps-arc/20220426072447.125975-1-geomatsi(a)gmail.com/T/#u
>
> IIUC, you have not yet sent a pull-request for next release. So probably
> it makes sense to squash this commit with b08a66fb680018b6 ("ARC: disasm:
> handle ARCv2 case in kprobe get/set functions").
Yes this is merge-window stuff so will go in next cycle.
I've added a fixup and push for-next.
Thx,
-Vineet
next prev parent reply other threads:[~2022-04-27 4:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 0:41 [vgupta-arc:for-next 3/4] arch/arc/kernel/disasm.c:494:23: error: 'struct pt_regs' has no member named 'gp'; did you mean 'fp'? kernel test robot
2022-04-26 0:41 ` kernel test robot
2022-04-26 7:31 ` Sergey Matyukevich
2022-04-26 7:31 ` Sergey Matyukevich
2022-04-27 4:04 ` Vineet Gupta [this message]
2022-04-27 4:04 ` Vineet Gupta
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=f87e457e-72fe-7d39-5045-3c8d2271f638@kernel.org \
--to=vgupta@kernel.org \
--cc=geomatsi@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-snps-arc@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.