Re: [PATCH] m68k/kernel - wire up syscall_trace_enter/leave for m68k

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Geert,

working on entry.S recently, I was reminded of this one. It's never been applied, and I can't find a trace of it in my tree.

Not sure how far Adrian got with seccomp support testing, so I'm uncertain this is still of interest ...

Cheers,

    Michael


On 28/08/20 8:58 pm, Geert Uytterhoeven wrote:
Hi Michael,

On Thu, Aug 27, 2020 at 9:29 PM Michael Schmitz <schmitzmic@xxxxxxxxx> wrote:
On 27/08/20 9:19 PM, Geert Uytterhoeven wrote:
On Thu, Aug 27, 2020 at 2:08 AM Michael Schmitz <schmitzmic@xxxxxxxxx> wrote:
On 26/08/20 11:23 PM, Geert Uytterhoeven wrote:
As your email subject didn't contain "v3", b4[*] insists on picking up
RFC v2, and refuses to pick up the latest version, even when forced
Argh - I thought that since the first two were tagged 'RFC', I could
just restart with v1.

Never heard of b4, sorry.
It's the new tool to download patches and patch series, adding
automatically any received *-by tags, and the Link: tag.  Makes my life
easier ;-)
I take that as read. Rather you than me :-)

Do you want me to resend this as v3? And any preference on the branch
test (non-zero, or -1)?
No need to resend, unless there will be a v4 ;-)

Gr{oetje,eeting}s,

                         Geert




[Index of Archives]     [Video for Linux]     [Yosemite News]     [Linux S/390]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux