On Tue, 4 Feb 2025 20:47:49 -0800
Davidlohr Bueso wrote:
> On Mon, 03 Feb 2025, Jonathan Cameron wrote:
>
> >On Tue, 22 Oct 2024 18:00:30 +0100
> >Jonathan Cameron wrote:
> >
> >> On Mon, 21 Oct 2024 20:23:46 -0700
> >> Davidlohr Bueso wrote:
> >>
> >> > On Tue, 27 Aug 2024, Jonathan Camer
On Mon, 03 Feb 2025, Jonathan Cameron wrote:
On Tue, 22 Oct 2024 18:00:30 +0100
Jonathan Cameron wrote:
On Mon, 21 Oct 2024 20:23:46 -0700
Davidlohr Bueso wrote:
> On Tue, 27 Aug 2024, Jonathan Cameron wrote:\n
> >No comments inline and LGTM. I'll queue it on my tree and push
> >that out on
On Tue, 22 Oct 2024 18:00:30 +0100
Jonathan Cameron wrote:
> On Mon, 21 Oct 2024 20:23:46 -0700
> Davidlohr Bueso wrote:
>
> > On Tue, 27 Aug 2024, Jonathan Cameron wrote:\n
> > >No comments inline and LGTM. I'll queue it on my tree and push
> > >that out on gitlab sometime soonish.
> >
On Mon, 21 Oct 2024 20:23:46 -0700
Davidlohr Bueso wrote:
> On Tue, 27 Aug 2024, Jonathan Cameron wrote:\n
> >No comments inline and LGTM. I'll queue it on my tree and push
> >that out on gitlab sometime soonish.
>
> I don't see this picked up, which is a good thing atm. While testing
> the ke
On Tue, 27 Aug 2024, Jonathan Cameron wrote:\n
No comments inline and LGTM. I'll queue it on my tree and push
that out on gitlab sometime soonish.
I don't see this picked up, which is a good thing atm. While testing
the kernel side, I noticed the following is needed, will send a v2
with it fold
On Tue, 13 Aug 2024 15:12:55 -0700
Davidlohr Bueso wrote:
> As of 3.1 spec, background commands can be canceled with a new
> abort command. Implement the support, which is advertised in
> the CEL. No ad-hoc context undoing is necessary as all the
> command logic of the running bg command is done
