lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 17 Aug 2022 15:38:31 +0200
From:   Cezary Rojewski <cezary.rojewski@...el.com>
To:     Takashi Iwai <tiwai@...e.de>,
        Amadeusz Sławiński 
        <amadeuszx.slawinski@...ux.intel.com>
CC:     Takashi Iwai <tiwai@...e.com>, <alsa-devel@...a-project.org>,
        <linux-kernel@...r.kernel.org>, Jaroslav Kysela <perex@...ex.cz>
Subject: Re: [RESEND][PATCH] ALSA: info: Fix llseek return value when using
 callback

On 2022-08-17 3:12 PM, Takashi Iwai wrote:

>> Doing resend, because I did copy paste mistake when pasting Takashi
>> email to git command, additionally alsa-devel blocked my previous
>> mail.
>> I've seen that Cezary already discussed this issue, and it doesn't
>> seem to be fixed, can this be somehow investigated? I guess we can
>> provide response we get from server when email fails?
> 
> It seems working now.  Jaroslav mentioned that it was some DNS
> problem.


Unfortunately the problem seems to still be there. Yesterday received 
"bad connection timeout" from Jaroslav (perex@...ex.cz, other recipients 
were not listed) for "[PATCH 2/2] ASoC: Intel: Skylake: try to get NHLT 
blob with PCM params as fallback" thread.

And now my reviewed-by email for recent Amadeo's series - "[PATCH 0/4] 
ALSA: hda: Minor cleanups" - was not delivered to 
alsa-devel@...a-project.org.


Regards,
Czarek

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ