From: Alexandru Dinu <alex.dinu07@gmail.com>
To: platform-driver-x86@vger.kernel.org
Subject: Re: Undelivered Mail Returned to Sender
Date: Wed, 16 Mar 2022 20:49:27 +0200 [thread overview]
Message-ID: <CAJOTRr4YzHO==FCsRF6kYkLs7MaUVc_RWEvcbnV9zn6-9946cw@mail.gmail.com> (raw)
In-Reply-To: <20220316184452.836313C4B1@lindbergh.monkeyblade.net>
Hi,
> I'll send out a v2 shortly: Alex, can you
> please retest when I do to make sure there aren't any regressions? None
> of these suggestions affect the core flow of how either of the
> workarounds work, so I'm not expecting any that wouldn't also reproduce
> on my EC backlight system that doesn't have either of these problems,
> but I can send you the updated version off-list first if you prefer.
It's ok either way. You can send me an updated version off-list.
> Alex, just FYI this was something that came to an AMD bug tracker and wanted you to be aware there are W/A going into nvidia-wmi-ec-backlight for some firmware problems with the mux.
> IIRC that was the original suspicion too on the bug reports.
Yes, thanks -- I followed this issue first:
https://gitlab.freedesktop.org/drm/amd/-/issues/1671.
> However I think it's still worth at least noting near the quirk in a comment
> what firmware version it was identified. If later there is confirmation that
> a particular firmware version had fixed it the quirk can be adjusted to be
> dropped.
That's a good tip. The laptop I tested this on (Lenovo Legion S7
15ACH6) originally shipped with:
UEFI: LENOVO v: HACN27WW date: 08/02/2021
There is an update to version HACN31WW (see lenovo support:
https://support.lenovo.com/ro/en/downloads/ds550201-bios-update-for-windows-10-64-bit-legion-s7-15ach6)
-- which I applied, however, the issue was not addressed, which seems
to be expected given the rather short /changelog:
HACN31WW
BIOS Notification :
1. Fixed
1) N/A.
2. Add
1) Add BOE0A1C support with Cookie and DR Key
3. Modified
1) Modify MinShortTerm & MinLongTerm PowerLimit value
EC Notification :
1. Fixed
1) None.
2. Add
1) None.
3. Modified
1)None.
> If you end up introducing a module parameter to try to activate these quirks
> it might be viable to ask the folks in those issues to try the v2 of your patch too
> when you're ready with the module parameter.
I posted a link to this mailing list to
https://gitlab.freedesktop.org/drm/amd/-/issues/1671, so people can be
aware and try to test.
Regards,
Alex
On Wed, 16 Mar 2022 at 20:45, Mail Delivery System
<MAILER-DAEMON@lindbergh.monkeyblade.net> wrote:
>
> This is the mail system at host lindbergh.monkeyblade.net.
>
> I'm sorry to have to inform you that your message could not
> be delivered to one or more recipients. It's attached below.
>
> For further assistance, please send mail to postmaster.
>
> If you do so, please include this problem report. You can
> delete your own text from the attached returned message.
>
> The mail system
>
> <platform-driver-x86@vger.kernel.org>: host 23.128.96.18[23.128.96.18] said:
> 550 5.7.1 Content-Policy reject msg: The message contains HTML subpart,
> therefore we consider it SPAM or Outlook Virus. TEXT/PLAIN is accepted.!
> BF:<U 0.5>; S1353677AbiCPSqF (in reply to end of DATA command)
>
>
>
> ---------- Forwarded message ----------
> From: Alexandru Dinu <alex.dinu07@gmail.com>
> To: platform-driver-x86@vger.kernel.org
> Cc:
> Bcc:
> Date: Wed, 16 Mar 2022 20:44:13 +0200
> Subject: Re: Undelivered Mail Returned to Sender
> Hi,
>
> > I'll send out a v2 shortly: Alex, can you
> > please retest when I do to make sure there aren't any regressions? None
> > of these suggestions affect the core flow of how either of the
> > workarounds work, so I'm not expecting any that wouldn't also reproduce
> > on my EC backlight system that doesn't have either of these problems,
> > but I can send you the updated version off-list first if you prefer.
>
> It's ok either way. You can send me an updated version off-list.
>
> > Alex, just FYI this was something that came to an AMD bug tracker and wanted you to be aware there are W/A going into nvidia-wmi-ec-backlight for some firmware problems with the mux.
> > IIRC that was the original suspicion too on the bug reports.
>
> Yes, thanks -- I followed this issue first: https://gitlab.freedesktop.org/drm/amd/-/issues/1671.
>
> > However I think it's still worth at least noting near the quirk in a comment
> > what firmware version it was identified. If later there is confirmation that
> > a particular firmware version had fixed it the quirk can be adjusted to be
> > dropped.
>
> That's a good tip. The laptop I tested this on (Lenovo Legion S7 15ACH6) originally shipped with:
>
> UEFI: LENOVO v: HACN27WW date: 08/02/2021
>
> There is an update to version HACN31WW (see lenovo support: https://support.lenovo.com/ro/en/downloads/ds550201-bios-update-for-windows-10-64-bit-legion-s7-15ach6) -- which I applied, however, the issue was not addressed, which seems to be expected given the rather short /changelog:
> HACN31WW
> BIOS Notification :
> 1. Fixed
> 1) N/A.
> 2. Add
> 1) Add BOE0A1C support with Cookie and DR Key
> 3. Modified
> 1) Modify MinShortTerm & MinLongTerm PowerLimit value
> EC Notification :
> 1. Fixed
> 1) None.
> 2. Add
> 1) None.
> 3. Modified
> 1)None.
>
> > If you end up introducing a module parameter to try to activate these quirks
> > it might be viable to ask the folks in those issues to try the v2 of your patch too
> > when you're ready with the module parameter.
>
> I posted a link to this mailing list to https://gitlab.freedesktop.org/drm/amd/-/issues/1671, so people can be aware and try to test.
> Regards,
> Alex
>
> On Wed, 16 Mar 2022 at 20:40, Mail Delivery System <MAILER-DAEMON@lindbergh.monkeyblade.net> wrote:
>>
>> This is the mail system at host lindbergh.monkeyblade.net.
>>
>> I'm sorry to have to inform you that your message could not
>> be delivered to one or more recipients. It's attached below.
>>
>> For further assistance, please send mail to postmaster.
>>
>> If you do so, please include this problem report. You can
>> delete your own text from the attached returned message.
>>
>> The mail system
>>
>> <platform-driver-x86@vger.kernel.org>: host 23.128.96.18[23.128.96.18] said:
>> 550 5.7.1 Content-Policy reject msg: The message contains HTML subpart,
>> therefore we consider it SPAM or Outlook Virus. TEXT/PLAIN is accepted.!
>> BF:<U 0.499997>; S240813AbiCPSkN (in reply to end of DATA command)
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Alexandru Dinu <alex.dinu07@gmail.com>
>> To: "Limonciello, Mario" <Mario.Limonciello@amd.com>
>> Cc: Daniel Dadap <ddadap@nvidia.com>, "Barnabás Pőcze" <pobrn@protonmail.com>, "platform-driver-x86@vger.kernel.org" <platform-driver-x86@vger.kernel.org>, Hans de Goede <hdegoede@redhat.com>, "markgross@kernel.org" <markgross@kernel.org>, "Deucher, Alexander" <Alexander.Deucher@amd.com>
>> Bcc:
>> Date: Wed, 16 Mar 2022 20:38:21 +0200
>> Subject: Re: [PATCH] nvidia-wmi-ec-backlight: Add workarounds for confused firmware
>> Hi,
>>
>>> > I'll send out a v2 shortly: Alex, can you
>>> please retest when I do to make sure there aren't any regressions? None
>>> of these suggestions affect the core flow of how either of the
>>> workarounds work, so I'm not expecting any that wouldn't also reproduce
>>> on my EC backlight system that doesn't have either of these problems,
>>> but I can send you the updated version off-list first if you prefer.
>>
>>
>> It's ok either way. You can send me an updated version off-list.
>>
>>> > Alex, just FYI this was something that came to an AMD bug tracker and wanted you to be aware there are W/A going into nvidia-wmi-ec-backlight for some firmware problems with the mux.
>>> IIRC that was the original suspicion too on the bug reports.
>>
>>
>> Yes, thanks -- I followed this issue first: https://gitlab.freedesktop.org/drm/amd/-/issues/1671.
>>
>>> > However I think it's still worth at least noting near the quirk in a comment
>>> what firmware version it was identified. If later there is confirmation that
>>> a particular firmware version had fixed it the quirk can be adjusted to be
>>> dropped.
>>
>>
>> That's a good tip. The laptop I tested this on (Lenovo Legion S7 15ACH6) originally shipped with:
>>
>> UEFI: LENOVO v: HACN27WW date: 08/02/2021
>>
>> There is an update to version HACN31WW (see lenovo support) -- which I applied, however, the issue was not addressed, which seems to be expected given the rather short /changelog:
>> HACN31WW
>> BIOS Notification :
>> 1. Fixed
>> 1) N/A.
>> 2. Add
>> 1) Add BOE0A1C support with Cookie and DR Key
>> 3. Modified
>> 1) Modify MinShortTerm & MinLongTerm PowerLimit value
>> EC Notification :
>> 1. Fixed
>> 1) None.
>> 2. Add
>> 1) None.
>> 3. Modified
>> 1)None.
>>>
>>> > If you end up introducing a module parameter to try to activate these quirks
>>> it might be viable to ask the folks in those issues to try the v2 of your patch too
>>> when you're ready with the module parameter.
>>
>>
>> I posted a link to this mailing list to https://gitlab.freedesktop.org/drm/amd/-/issues/1671, so people can be aware and try to test.
>>
>> Regards,
>> Alex
>>
>> On Wed, 16 Mar 2022 at 20:25, Limonciello, Mario <Mario.Limonciello@amd.com> wrote:
>>>
>>> [Public]
>>>
>>> > >
>>> > > IIRC this is the bug you want linked in the commit message:
>>> > >
>>> > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitla
>>> > b.freedesktop.org%2Fdrm%2Famd%2F-
>>> > %2Fissues%2F1671&data=04%7C01%7CMario.Limonciello%40amd.com
>>> > %7C5559a4f23f46426add1808da0773b4ac%7C3dd8961fe4884e608e11a82d994
>>> > e183d%7C0%7C0%7C637830490785879396%7CUnknown%7CTWFpbGZsb3d8
>>> > eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
>>> > D%7C3000&sdata=P%2FBcLeN9rnjGam4kh68ZQUBAPIDM4G%2Bk1ukb5
>>> > k%2BRFVg%3D&reserved=0
>>> >
>>> >
>>> > Ah, thanks. Most of the people on this bug seem like their problem was
>>> > that they didn't have the nvidia-wmi-ec-backlight driver, which also
>>> > didn't exist at the time the bug was filed. There is one person with a
>>> > newer comment reporting behavior that sounds like what this patch works
>>> > around, and it is the same person who initially reported the issue to me. :)
>>> >
>>> >
>>>
>>> Thanks for looking at those.
>>>
>>> > > But these two look possible to be the same root cause:
>>> > >
>>> > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitla
>>> > b.freedesktop.org%2Fdrm%2Famd%2F-
>>> > %2Fissues%2F1791&data=04%7C01%7CMario.Limonciello%40amd.com
>>> > %7C5559a4f23f46426add1808da0773b4ac%7C3dd8961fe4884e608e11a82d994
>>> > e183d%7C0%7C0%7C637830490785879396%7CUnknown%7CTWFpbGZsb3d8
>>> > eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
>>> > D%7C3000&sdata=Bv3lJJOG7BZxlvizh0L4gmHgakzjlJkl7TqGh9HTho4%3D
>>> > &reserved=0
>>> >
>>> >
>>> > This one sounds like it might be a different issue, since it was
>>> > apparently working at some point with a kernel that didn't have the EC
>>> > backlight driver, and then not working on a newer kernel that also
>>> > didn't have the EC backlight driver. That is, of course, assuming
>>> > vanilla kernels: it is certainly possible that the EC backlight driver
>>> > was backported.
>>> >
>>> > >
>>> > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitla
>>> > b.freedesktop.org%2Fdrm%2Famd%2F-
>>> > %2Fissues%2F1794&data=04%7C01%7CMario.Limonciello%40amd.com
>>> > %7C5559a4f23f46426add1808da0773b4ac%7C3dd8961fe4884e608e11a82d994
>>> > e183d%7C0%7C0%7C637830490785879396%7CUnknown%7CTWFpbGZsb3d8
>>> > eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
>>> > D%7C3000&sdata=JfUhLPRIMVLypLXoAxKhpSw7WIN4M%2BS4Y48MQ
>>> > %2BzXdbk%3D&reserved=0
>>> >
>>> >
>>> > This sounds like it could possibly be a simple case of not having the EC
>>> > backlight driver. Notably, the backlight device exposed by the amdgpu
>>> > driver never works, in contrast to the system these workarounds are
>>> > targeting, where the amdgpu driver's backlight device initially works,
>>> > but then stops working after the first suspend/resume cycle (and the EC
>>> > backlight driver doesn't work initially, but then starts working after
>>> > suspend/resume).
>>>
>>> I guess when we see backlight issues on these A+N designs the checks should be:
>>> 1) Are they supposed to be using the nvidia-wmi-ec-backlight driver?
>>> 2) Is their kernel new enough to have it?
>>> 3) Do they have the config enabled?
>>>
>>> Do you have a script or could you perhaps include some documentation we can
>>> point people to check "1" so we don't always have to go tear apart ACPI tables
>>> and make guesses?
>>>
>>> I guess it's something like grab _WDG and then parse it to see if there is an entry.
>>>
>>> >
>>> >
>>> > >
>>> > > If you end up introducing a module parameter to try to activate these
>>> > quirks
>>> > > it might be viable to ask the folks in those issues to try the v2 of your patch
>>> > too
>>> > > when you're ready with the module parameter.
>>> > >
>>> >
>>> > v1 already has the quirks plumbed up to module parameters (those module
>>> > parameters just don't have corresponding sysfs entries). In any case, I
>>> > only see one report between those bugs that sounds like the issue these
>>> > WARs are meant to address, and since it's from the same reporter, it
>>> > sounds like we won't need to be adding any additional quirks table
>>> > entries right away.
>>> >
>>> >
>>> > >>
>>> > >>> Comments inline as well.
>>> > >>>
>>> > >>>> -----Original Message-----
>>> > >>>> From: Daniel Dadap <ddadap@nvidia.com>
>>> > >>>> Sent: Wednesday, March 16, 2022 10:11
>>> > >>>> To: Barnabás Pőcze <pobrn@protonmail.com>
>>> > >>>> Cc: platform-driver-x86@vger.kernel.org; Alexandru Dinu
>>> > >>>> <alex.dinu07@gmail.com>; Hans de Goede <hdegoede@redhat.com>;
>>> > >>>> markgross@kernel.org
>>> > >>>> Subject: Re: [PATCH] nvidia-wmi-ec-backlight: Add workarounds for
>>> > >>>> confused firmware
>>> > >>>>
>>> > >> [ ... ]
>>> > >>
>>> > >>
>>> > >>>> On 3/15/22 9:50 PM, Barnabás Pőcze wrote:
>>> > >>>>> [ ... ]
>>> > >>>>> Lastly, is it expected that these bugs will be properly fixed?
>>> > >>>> Possibly, but I wouldn't hold out hope for it for an issue at this scale
>>> > >>>> on an already shipping system.
>>> > >>> This question I'm assuming was aimed at narrowing the quirk to only
>>> > >>> match certain FW versions or so. If there is no certainty of when/if it
>>> > >>> will be fixed I agree with current direction.
>>> > >>> However I think it's still worth at least noting near the quirk in a
>>> > comment
>>> > >>> what firmware version it was identified. If later there is confirmation
>>> > that
>>> > >>> a particular firmware version had fixed it the quirk can be adjusted to be
>>> > >>> dropped.
>>> > >>>
>>> > >> Thanks, Mario. Sure, I'll make sure the firmware version this was first
>>> > >> observed in is noted.
>>> > >>
>>> > >>
next parent reply other threads:[~2022-03-16 18:50 UTC|newest]
Thread overview: 287+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220316184452.836313C4B1@lindbergh.monkeyblade.net>
2022-03-16 18:49 ` Alexandru Dinu [this message]
[not found] <4Svb6P0lWsz3wZY@mail-02.mail-europe.com>
2023-12-19 12:19 ` Undelivered Mail Returned to Sender Zounp
2023-12-19 13:22 ` Kerin Millar
2023-08-07 7:09 Mail Delivery System
-- strict thread matches above, loose matches on Subject: below --
2023-02-19 19:40 Mail Delivery System
2023-02-15 0:29 Mail Delivery System
2023-02-12 5:24 Mail Delivery System
2023-02-11 21:14 Mail Delivery System
2023-02-11 20:10 Mail Delivery System
2023-02-11 19:19 Mail Delivery System
2023-02-10 17:55 Mail Delivery System
2023-02-10 4:18 Mail Delivery System
2023-02-09 16:04 Mail Delivery System
2023-02-08 20:14 Mail Delivery System
2023-02-08 18:46 Mail Delivery System
2023-02-08 11:15 Mail Delivery System
2023-02-07 23:20 Mail Delivery System
2023-02-04 21:42 Mail Delivery System
2023-01-30 12:17 Mail Delivery System
2023-01-26 6:38 Mail Delivery System
2023-01-20 19:38 Mail Delivery System
2023-01-16 10:54 Mail Delivery System
2022-09-22 2:36 Mail Delivery System
2022-09-17 15:03 Mail Delivery System
2022-08-29 11:30 Mail Delivery System
2022-08-04 12:05 Mail Delivery System
2022-07-22 22:50 Mail Delivery System
[not found] <20220608153543.6621CCE36@lindbergh.monkeyblade.net>
2022-06-08 15:39 ` Brian Bunker
2022-05-28 3:49 Mail Delivery System
2022-05-19 5:41 Mail Delivery System
2022-04-25 3:12 Mail Delivery System
[not found] <20220216022900.8DE3E1770A1@mail-01.amsat.org>
2022-02-16 3:20 ` Fwd: " Akihiko Odaki
[not found] ` <PH0PR16MB476031694D02A6550B15D294B6359@PH0PR16MB4760.namprd16.prod.outlook.com>
2022-02-16 15:17 ` Philippe Mathieu-Daudé via
2021-11-11 12:18 Mail Delivery System
2021-10-18 16:27 Mail Delivery System
2021-10-15 8:31 Mail Delivery System
[not found] <20210714174004.3CC94C06175F@lindbergh.monkeyblade.net>
2021-07-14 17:42 ` Hylke Hellinga
2021-07-14 17:45 ` Hylke Hellinga
[not found] <20210114204233.4E53323AFC@mail.kernel.org>
[not found] ` <20210114210253.GE1164248@magnolia>
[not found] ` <87455a93-7f61-d056-df10-9d574303f875@kernel.org>
2021-01-15 0:39 ` Darrick J. Wong
[not found] <20200818152940.383D9C061342@lindbergh.monkeyblade.net>
2020-08-18 15:32 ` Fwd: " Rushil Umaretiya
2020-08-20 10:54 ` Stefan Puiu
[not found] <20170813010827.487F4181D3417@smtprelay07.hostedemail.com>
2017-08-13 1:49 ` Joe Perches
2015-06-20 16:36 Mail Delivery System
2015-06-19 14:19 Mail Delivery System
2015-06-12 12:21 Mail Delivery System
2015-04-30 12:09 Mail Delivery System
2015-03-25 17:06 Mail Delivery System
2015-02-28 12:54 Mail Delivery System
[not found] <20150221210915.3734E341F916@elvis.mu.org>
2015-02-21 21:18 ` Alfred Perlstein
2015-01-28 22:50 Mail Delivery System
2014-12-09 3:22 Mail Delivery System
2014-11-05 1:58 Mail Delivery System
2014-11-05 1:53 Mail Delivery System
2014-11-04 19:35 Mail Delivery System
2014-10-13 6:16 Mail Delivery System
2014-10-10 14:49 Mail Delivery System
2014-10-08 0:14 Mail Delivery System
2014-10-07 2:09 Mail Delivery System
2014-10-02 13:13 Mail Delivery System
2014-09-10 14:33 Mail Delivery System
2014-08-28 7:37 Mail Delivery System
2014-08-28 6:41 Mail Delivery System
2014-08-28 5:22 Mail Delivery System
2014-08-27 21:36 Mail Delivery System
2014-08-27 21:02 Mail Delivery System
2014-08-16 4:25 Mail Delivery System
2014-08-13 22:38 Mail Delivery System
2014-08-04 11:39 Mail Delivery System
2014-08-04 3:42 Mail Delivery System
2014-08-04 0:26 Mail Delivery System
2014-07-30 16:08 Mail Delivery System
2014-07-23 19:32 Mail Delivery System
2014-07-23 19:01 Mail Delivery System
2014-07-23 10:16 Mail Delivery System
2014-07-23 7:46 Mail Delivery System
2014-07-23 4:47 Mail Delivery System
2014-07-21 19:51 Mail Delivery System
2014-02-21 12:32 Mail Delivery System
2014-02-21 4:05 Mail Delivery System
2014-02-18 0:47 Mail Delivery System
2014-02-17 11:36 Mail Delivery System
2014-02-16 23:49 Mail Delivery System
2014-02-16 23:49 Mail Delivery System
2014-02-16 23:49 Mail Delivery System
2014-02-16 23:49 Mail Delivery System
2014-02-16 23:49 Mail Delivery System
2014-02-16 23:49 Mail Delivery System
2014-02-16 23:49 Mail Delivery System
2014-02-16 23:49 Mail Delivery System
2014-02-16 23:49 Mail Delivery System
2014-02-16 23:49 Mail Delivery System
2013-07-02 16:03 Mail Delivery System
2013-03-30 4:13 Mail Delivery System
2013-03-25 20:16 Mail Delivery System
2013-03-25 13:18 Mail Delivery System
2013-03-25 13:08 Mail Delivery System
2013-03-25 10:46 Mail Delivery System
2013-03-25 10:20 Mail Delivery System
2013-03-25 8:32 Mail Delivery System
2013-03-25 7:53 Mail Delivery System
2013-03-25 7:25 Mail Delivery System
2013-03-25 5:12 Mail Delivery System
2013-03-25 4:50 Mail Delivery System
2013-03-25 2:52 Mail Delivery System
2012-11-01 17:37 Mail Delivery System
2012-10-29 4:13 Mail Delivery System
2012-10-29 2:57 Mail Delivery System
2012-10-25 4:59 Mail Delivery System
2012-10-22 23:57 Mail Delivery System
2012-10-22 23:00 Mail Delivery System
2012-10-22 22:30 Mail Delivery System
2012-10-18 9:38 Mail Delivery System
2012-10-17 19:55 Mail Delivery System
2012-10-17 11:53 Mail Delivery System
2012-10-17 8:20 Mail Delivery System
2012-10-17 4:48 Mail Delivery System
2012-09-15 4:32 Mail Delivery System
2012-08-31 3:09 Mail Delivery System
2012-08-30 7:21 Mail Delivery System
2012-08-29 12:26 Mail Delivery System
2012-08-28 7:04 Mail Delivery System
2012-08-27 2:58 Mail Delivery System
2012-08-23 17:13 Mail Delivery System
2012-08-14 4:56 Mail Delivery System
2012-06-11 2:22 Mail Delivery System
2012-05-11 0:09 Mail Delivery System
2012-05-10 19:08 Mail Delivery System
2012-05-10 15:05 Mail Delivery System
2012-05-10 2:09 Mail Delivery System
2012-05-10 0:15 Mail Delivery System
2012-05-09 19:57 Mail Delivery System
2012-05-09 8:39 Mail Delivery System
2012-05-03 1:08 postmaster-noreply-FMRk+c35SBqonA0d6jMUrA
2012-04-12 18:46 Mail Delivery System
2012-04-12 18:29 Mail Delivery System
2012-04-12 0:52 Mail Delivery System
2012-04-11 12:35 Mail Delivery System
2012-04-11 11:02 postmaster-noreply-FMRk+c35SBqonA0d6jMUrA
2012-04-11 8:36 postmaster-noreply-FMRk+c35SBqonA0d6jMUrA
2012-04-11 6:56 Mail Delivery System
2012-04-11 6:54 Mail Delivery System
2012-04-11 6:32 Mail Delivery System
2012-04-11 1:48 Mail Delivery System
2012-04-10 17:26 postmaster-noreply-FMRk+c35SBqonA0d6jMUrA
2012-04-09 14:12 Mail Delivery System
2012-04-03 9:11 Mail Delivery System
2012-04-03 0:37 postmaster-noreply-FMRk+c35SBqonA0d6jMUrA
2012-04-02 23:59 postmaster-noreply-FMRk+c35SBqonA0d6jMUrA
2012-04-02 23:34 Mail Delivery System
2012-04-02 21:57 postmaster-noreply-FMRk+c35SBqonA0d6jMUrA
2012-03-31 0:48 Mail Delivery System
2012-03-30 17:45 Mail Delivery System
2012-03-30 3:45 Mail Delivery System
2012-03-26 21:48 Mail Delivery System
2012-03-13 11:03 Mail Delivery System
2012-03-07 22:52 Mail Delivery System
2012-03-01 23:37 Mail Delivery System
2012-03-01 13:47 Mail Delivery System
2012-03-01 13:22 Mail Delivery System
2012-02-29 11:44 Mail Delivery System
2012-02-22 23:09 Mail Delivery System
2012-02-22 18:13 Mail Delivery System
2012-02-22 8:19 Mail Delivery System
2012-02-21 5:42 Mail Delivery System
2012-02-21 1:48 Mail Delivery System
2012-01-29 12:35 Mail Delivery System
2012-01-28 3:53 Mail Delivery System
2012-01-26 9:06 Mail Delivery System
2012-01-24 9:27 Mail Delivery System
2012-01-19 1:54 Mail Delivery System
2012-01-18 20:06 Mail Delivery System
2012-01-18 18:44 Mail Delivery System
2012-01-18 8:37 Mail Delivery System
2012-01-04 0:28 Mail Delivery System
2011-12-20 22:39 Mail Delivery System
2011-12-19 19:10 Mail Delivery System
2011-12-10 1:50 Mail Delivery System
2011-12-09 19:39 Mail Delivery System
2011-12-06 14:54 Mail Delivery System
2011-12-06 14:54 Mail Delivery System
2011-12-06 14:54 Mail Delivery System
2011-12-06 14:54 Mail Delivery System
2011-12-06 14:54 Mail Delivery System
2011-12-05 21:14 Mail Delivery System
2011-12-03 12:46 Mail Delivery System
2011-12-03 8:24 Mail Delivery System
2011-12-01 2:29 Mail Delivery System
2011-11-30 22:39 Mail Delivery System
2011-11-30 5:01 Mail Delivery System
2011-11-26 0:07 Mail Delivery System
2011-11-20 10:21 Mail Delivery System
2011-11-19 11:19 Mail Delivery System
2011-11-17 15:46 Mail Delivery System
2011-11-17 12:58 Mail Delivery System
2011-11-17 11:13 Mail Delivery System
2011-11-15 15:20 Mail Delivery System
2011-11-15 11:22 Mail Delivery System
2011-11-15 11:21 Mail Delivery System
2011-11-08 13:47 Mail Delivery System
2011-11-03 13:40 Mail Delivery System
2011-11-01 16:48 Mail Delivery System
2011-10-27 10:45 Mail Delivery System
2010-12-05 18:50 Unknown, MAILER-DAEMON
2010-12-04 20:20 Unknown, MAILER-DAEMON
2007-08-26 13:52 Mail Delivery System
2007-04-27 4:39 Mail Delivery System
2007-03-19 0:06 Mail Delivery System
2007-03-09 20:29 Mail Delivery System
2007-03-08 5:23 Mail Delivery System
2007-03-07 22:32 Mail Delivery System
2007-02-23 21:13 Mail Delivery System
2007-02-23 21:13 Mail Delivery System
2007-02-23 14:53 Mail Delivery System
2007-02-21 11:31 Mail Delivery System
2007-02-21 11:31 Mail Delivery System
2007-02-20 11:27 Mail Delivery System
2007-02-20 5:04 Mail Delivery System
2007-02-20 2:10 Mail Delivery System
2007-02-19 16:05 Mail Delivery System
2007-02-18 12:17 Mail Delivery System
2007-02-17 12:58 Mail Delivery System
2007-02-15 22:35 Mail Delivery System
2007-02-13 8:57 Mail Delivery System
2007-02-10 0:27 Mail Delivery System
2007-02-06 11:28 Mail Delivery System
2007-02-04 11:31 Mail Delivery System
2007-02-04 3:05 Mail Delivery System
2007-02-01 19:06 Mail Delivery System
2007-01-19 0:01 Mail Delivery System
2007-01-11 14:42 Mail Delivery System
2006-12-22 3:46 Mail Delivery System
2006-12-09 0:29 Mail Delivery System
2006-12-08 23:32 Mail Delivery System
2006-12-08 12:51 Mail Delivery System
2006-12-04 1:14 Mail Delivery System
2006-12-02 22:45 Mail Delivery System
2006-12-02 10:59 Mail Delivery System
2006-12-01 23:42 Mail Delivery System
2006-11-30 8:06 Mail Delivery System
2006-11-24 20:07 Mail Delivery System
2006-11-24 19:02 Mail Delivery System
2006-11-22 6:56 Mail Delivery System
2006-11-21 6:35 Mail Delivery System
2006-11-18 12:17 Mail Delivery System
2006-11-17 11:42 Mail Delivery System
2006-11-14 7:35 Mail Delivery System
2006-11-14 6:56 Mail Delivery System
2006-11-08 15:21 Mail Delivery System
2006-11-08 5:54 Mail Delivery System
2006-11-07 14:45 Mail Delivery System
2006-11-07 5:11 Mail Delivery System
2006-11-06 14:11 Mail Delivery System
2006-10-30 15:04 Mail Delivery System
2006-10-30 9:39 Mail Delivery System
2006-10-29 8:18 Mail Delivery System
2006-10-27 16:45 Mail Delivery System
2006-09-19 7:06 Mail Delivery System
2006-07-27 22:16 Mail Delivery System
2006-07-27 14:57 Mail Delivery System
2006-07-26 16:39 Mail Delivery System
2006-07-22 19:08 Mail Delivery System
2006-05-12 17:35 Mail Delivery System
2006-04-13 19:13 Mail Delivery System
2006-04-01 6:02 Mail Delivery System
2006-01-22 20:18 Mail Delivery System
2006-01-16 14:57 Mail Delivery System
[not found] <20060107100533.CED1E21456@linux.site>
2006-01-09 10:03 ` Alan Jenkins
2005-09-21 14:22 Mail Delivery System
2005-09-19 23:39 Mail Delivery System
2004-11-10 11:13 Mail Delivery System
2004-11-09 2:13 Mail Delivery System
2004-11-06 18:45 Mail Delivery System
2004-10-27 20:41 Mail Delivery System
2004-10-25 2:06 Mail Delivery System
2004-09-23 4:25 Mail Delivery System
2004-09-22 9:48 Mail Delivery System
2004-09-22 6:26 Mail Delivery System
2004-09-22 3:19 Mail Delivery System
2004-09-21 14:56 Mail Delivery System
2004-09-21 12:03 Mail Delivery System
2004-04-09 7:28 Mail Delivery System
2004-02-28 13:39 Mail Delivery System
2004-01-27 1:40 Mail Delivery System
2003-09-04 3:06 Mail Delivery System
2003-08-28 3:07 Mail Delivery System
2003-08-26 2:59 Mail Delivery System
2003-08-20 22:32 Mail Delivery System
2003-07-05 23:10 Mail Delivery System
2001-12-07 18:41 Mail Delivery System
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='CAJOTRr4YzHO==FCsRF6kYkLs7MaUVc_RWEvcbnV9zn6-9946cw@mail.gmail.com' \
--to=alex.dinu07@gmail.com \
--cc=platform-driver-x86@vger.kernel.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.