Em 01/07/2025 13:44, Riana Tauro escreveu:
On 7/1/2025 9:32 PM, Raag Jadav wrote:
On Tue, Jul 01, 2025 at 04:35:42PM +0200, Christian König wrote:
On 01.07.25 16:23, Raag Jadav wrote:
On Tue, Jul 01, 2025 at 05:11:24PM +0530, Riana Tauro wrote:
On 7/1/2025 5:07 PM, Riana Tauro wrote:
On 6/
On 7/1/2025 9:32 PM, Raag Jadav wrote:
On Tue, Jul 01, 2025 at 04:35:42PM +0200, Christian König wrote:
On 01.07.25 16:23, Raag Jadav wrote:
On Tue, Jul 01, 2025 at 05:11:24PM +0530, Riana Tauro wrote:
On 7/1/2025 5:07 PM, Riana Tauro wrote:
On 6/30/2025 11:03 PM, Rodrigo Vivi wrote:
On M
On Tue, Jul 01, 2025 at 04:35:42PM +0200, Christian König wrote:
>On 01.07.25 16:23, Raag Jadav wrote:
>> On Tue, Jul 01, 2025 at 05:11:24PM +0530, Riana Tauro wrote:
>>> On 7/1/2025 5:07 PM, Riana Tauro wrote:
On 6/30/2025 11:03 PM, Rodrigo Vivi wrote:
> On Mon, Jun 30, 2025 at 10:29:10AM
On 01.07.25 16:23, Raag Jadav wrote:
> On Tue, Jul 01, 2025 at 05:11:24PM +0530, Riana Tauro wrote:
>> On 7/1/2025 5:07 PM, Riana Tauro wrote:
>>> On 6/30/2025 11:03 PM, Rodrigo Vivi wrote:
On Mon, Jun 30, 2025 at 10:29:10AM +0200, Christian König wrote:
> On 27.06.25 23:38, Rodrigo Vivi w
On Tue, Jul 01, 2025 at 05:11:24PM +0530, Riana Tauro wrote:
> On 7/1/2025 5:07 PM, Riana Tauro wrote:
> > On 6/30/2025 11:03 PM, Rodrigo Vivi wrote:
> > > On Mon, Jun 30, 2025 at 10:29:10AM +0200, Christian König wrote:
> > > > On 27.06.25 23:38, Rodrigo Vivi wrote:
> > > > > > > Or at least print
On 7/1/2025 5:07 PM, Riana Tauro wrote:
Hi Rodrigo/Christian
On 6/30/2025 11:03 PM, Rodrigo Vivi wrote:
On Mon, Jun 30, 2025 at 10:29:10AM +0200, Christian König wrote:
On 27.06.25 23:38, Rodrigo Vivi wrote:
Or at least print a big warning into the system log?
I mean a firmware update is
Hi Rodrigo/Christian
On 6/30/2025 11:03 PM, Rodrigo Vivi wrote:
On Mon, Jun 30, 2025 at 10:29:10AM +0200, Christian König wrote:
On 27.06.25 23:38, Rodrigo Vivi wrote:
Or at least print a big warning into the system log?
I mean a firmware update is usually something which the system administr
On Mon, Jun 30, 2025 at 10:29:10AM +0200, Christian König wrote:
> On 27.06.25 23:38, Rodrigo Vivi wrote:
> >>> Or at least print a big warning into the system log?
> >>>
> >>> I mean a firmware update is usually something which the system
> >>> administrator triggers very explicitly because when
On 27.06.25 23:38, Rodrigo Vivi wrote:
>>> Or at least print a big warning into the system log?
>>>
>>> I mean a firmware update is usually something which the system
>>> administrator triggers very explicitly because when it fails for some
>>> reason (e.g. unexpected reset, power outage or whate
On Tue, Jun 24, 2025 at 05:36:29PM -0400, Rodrigo Vivi wrote:
> On Tue, Jun 24, 2025 at 04:23:31PM +0200, Christian König wrote:
> > On 24.06.25 16:03, Riana Tauro wrote:
> > > Hi Christian
> > >
> > > On 6/24/2025 5:56 PM, Christian König wrote:
> > >> On 23.06.25 12:01, Riana Tauro wrote:
> > >>
On Tue, Jun 24, 2025 at 04:23:31PM +0200, Christian König wrote:
> On 24.06.25 16:03, Riana Tauro wrote:
> > Hi Christian
> >
> > On 6/24/2025 5:56 PM, Christian König wrote:
> >> On 23.06.25 12:01, Riana Tauro wrote:
> >>> A device is declared wedged when it is non-recoverable from
> >>> the driv
On 24.06.25 16:03, Riana Tauro wrote:
> Hi Christian
>
> On 6/24/2025 5:56 PM, Christian König wrote:
>> On 23.06.25 12:01, Riana Tauro wrote:
>>> A device is declared wedged when it is non-recoverable from
>>> the driver context.
>>
>> Well, not quite.
>
> i took this from the below document. Sh
Hi Christian
On 6/24/2025 5:56 PM, Christian König wrote:
On 23.06.25 12:01, Riana Tauro wrote:
A device is declared wedged when it is non-recoverable from
the driver context.
Well, not quite.
i took this from the below document. Should it be changed?
https://www.kernel.org/doc/html/v6.16-
13 matches
Mail list logo
