Re: [PATCH v4 0/3] Use proper printk format in appletbdrm

2025-04-21 Thread Alyssa Rosenzweig
On Tue, 08 Apr 2025 12:17:13 +0530, Aditya Garg wrote: > The vsprint patch was originally being sent as a seperate patch [1], and > I was waiting it to be taken up. But as suggested by Petr, I'm sending > them via DRM. > > v2: > Remove printf tests, will merge later through Kees' tree > > [...]

Re: [PATCH v4 0/3] Use proper printk format in appletbdrm

2025-04-21 Thread Aditya Garg
On 21-04-2025 07:26 pm, Alyssa Rosenzweig wrote: >> Any change needed or just because some other maintainer manages this? >> Although Tbh, I really don't care about backporting since T2 Mac users are >> still using patched kernels provided by us. I'd rather free my mind in >> getting this don

Re: [PATCH v4 0/3] Use proper printk format in appletbdrm

2025-04-21 Thread Alyssa Rosenzweig
> Any change needed or just because some other maintainer manages this? > Although Tbh, I really don't care about backporting since T2 Mac users are > still using patched kernels provided by us. I'd rather free my mind in > getting this done. I'm just too new to kernel to do nontrivial merges.

Re: [PATCH v4 0/3] Use proper printk format in appletbdrm

2025-04-21 Thread Aditya Garg
On 21-04-2025 07:19 pm, Alyssa Rosenzweig wrote: > I didn't realize this was so subtle with the backporting. I don't think > I can take this on, sorry. Any change needed or just because some other maintainer manages this? Although Tbh, I really don't care about backporting since T2 Mac users a

Re: [PATCH v4 0/3] Use proper printk format in appletbdrm

2025-04-21 Thread Alyssa Rosenzweig
I didn't realize this was so subtle with the backporting. I don't think I can take this on, sorry. Le Mon, Apr 21, 2025 at 06:40:23PM +0530, Aditya Garg a écrit : > > > On 21-04-2025 06:38 pm, Aditya Garg wrote: > > > > > > On 21-04-2025 06:37 pm, Alyssa Rosenzweig wrote: > >>> On 21-04-2025 0

Re: [PATCH v4 0/3] Use proper printk format in appletbdrm

2025-04-21 Thread Aditya Garg
On 21-04-2025 06:38 pm, Aditya Garg wrote: > > > On 21-04-2025 06:37 pm, Alyssa Rosenzweig wrote: >>> On 21-04-2025 05:35 pm, Alyssa Rosenzweig wrote: > Can I have a feedback from some DRM maintainer on this? AFAIK merge > window is over for some time now. It's been more than a week a

Re: [PATCH v4 0/3] Use proper printk format in appletbdrm

2025-04-21 Thread Aditya Garg
On 21-04-2025 06:37 pm, Alyssa Rosenzweig wrote: >> On 21-04-2025 05:35 pm, Alyssa Rosenzweig wrote: Can I have a feedback from some DRM maintainer on this? AFAIK merge window is over for some time now. It's been more than a week and last time when I submitted, it just stayed in

Re: [PATCH v4 0/3] Use proper printk format in appletbdrm

2025-04-21 Thread Alyssa Rosenzweig
> On 21-04-2025 05:35 pm, Alyssa Rosenzweig wrote: > >> Can I have a feedback from some DRM maintainer on this? AFAIK merge window > >> is over for some time now. It's been more than a week and last time when I > >> submitted, it just stayed in the mailing list without any feedback. > > > > DRM

Re: [PATCH v4 0/3] Use proper printk format in appletbdrm

2025-04-21 Thread Aditya Garg
On 21-04-2025 05:35 pm, Alyssa Rosenzweig wrote: >> Can I have a feedback from some DRM maintainer on this? AFAIK merge window >> is over for some time now. It's been more than a week and last time when I >> submitted, it just stayed in the mailing list without any feedback. > > DRM hides the

Re: [PATCH v4 0/3] Use proper printk format in appletbdrm

2025-04-21 Thread Alyssa Rosenzweig
> Can I have a feedback from some DRM maintainer on this? AFAIK merge window is > over for some time now. It's been more than a week and last time when I > submitted, it just stayed in the mailing list without any feedback. DRM hides the merge window from committers so that's not super relevant.

Re: [PATCH v4 0/3] Use proper printk format in appletbdrm

2025-04-17 Thread Aditya Garg
Hi On 08-04-2025 12:17 pm, Aditya Garg wrote: > The vsprint patch was originally being sent as a seperate patch [1], and > I was waiting it to be taken up. But as suggested by Petr, I'm sending > them via DRM. > > v2: > Remove printf tests, will merge later through Kees' tree > > v3: > Re-add

Re: [PATCH v4 0/3] Use proper printk format in appletbdrm

2025-04-09 Thread Petr Mladek
On Tue 2025-04-08 12:38:50, Andy Shevchenko wrote: > On Tue, Apr 08, 2025 at 08:52:10AM +, Aditya Garg wrote: > > > On 8 Apr 2025, at 2:11 PM, Andy Shevchenko > > > wrote: > > > On Tue, Apr 08, 2025 at 12:17:13PM +0530, Aditya Garg wrote: > > >> The vsprint patch was originally being sent as

Re: [PATCH v4 0/3] Use proper printk format in appletbdrm

2025-04-08 Thread Andy Shevchenko
On Tue, Apr 08, 2025 at 08:52:10AM +, Aditya Garg wrote: > > On 8 Apr 2025, at 2:11 PM, Andy Shevchenko > > wrote: > > On Tue, Apr 08, 2025 at 12:17:13PM +0530, Aditya Garg wrote: > >> The vsprint patch was originally being sent as a seperate patch [1], and > >> I was waiting it to be taken u

[PATCH v4 0/3] Use proper printk format in appletbdrm

2025-04-08 Thread Aditya Garg
The vsprint patch was originally being sent as a seperate patch [1], and I was waiting it to be taken up. But as suggested by Petr, I'm sending them via DRM. v2: Remove printf tests, will merge later through Kees' tree v3: Re-add printf tests, since 6.15-rc1 has the necessary commits merged now.

Re: [PATCH v4 0/3] Use proper printk format in appletbdrm

2025-04-08 Thread Aditya Garg
> On 8 Apr 2025, at 2:11 PM, Andy Shevchenko > wrote: > > On Tue, Apr 08, 2025 at 12:17:13PM +0530, Aditya Garg wrote: >> The vsprint patch was originally being sent as a seperate patch [1], and >> I was waiting it to be taken up. But as suggested by Petr, I'm sending >> them via DRM. > > Yo

Re: [PATCH v4 0/3] Use proper printk format in appletbdrm

2025-04-08 Thread Andy Shevchenko
On Tue, Apr 08, 2025 at 12:17:13PM +0530, Aditya Garg wrote: > The vsprint patch was originally being sent as a seperate patch [1], and > I was waiting it to be taken up. But as suggested by Petr, I'm sending > them via DRM. You need to do something about your tools, really. Now it's patch 3 threa