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]
Message-ID: <20200918094451.000033cc@Huawei.com>
Date:   Fri, 18 Sep 2020 09:44:51 +0100
From:   Jonathan Cameron <Jonathan.Cameron@...wei.com>
To:     Sean V Kelley <sean.v.kelley@...el.com>
CC:     Bjorn Helgaas <helgaas@...nel.org>, <bhelgaas@...gle.com>,
        <rjw@...ysocki.net>, <ashok.raj@...el.com>, <tony.luck@...el.com>,
        <sathyanarayanan.kuppuswamy@...ux.intel.com>,
        <qiuxu.zhuo@...el.com>, <linux-pci@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V4 00/10] Add RCEC handling to PCI/AER

On Thu, 17 Sep 2020 10:55:16 -0700
Sean V Kelley <sean.v.kelley@...el.com> wrote:

> On 17 Sep 2020, at 10:36, Bjorn Helgaas wrote:
> 
> > On Thu, Sep 17, 2020 at 09:25:38AM -0700, Sean V Kelley wrote:  
> >> Changes since v3 [1]:  
> >
> > This series claims "V4 00/10", i.e., there should be this cover letter
> > plus 10 patches, but I only got 3 patches.  I don't know if some got
> > lost, or if only those 3 patches were updated, or what?  If it's the
> > latter, it's too hard for me to collect the right versions of
> > everything into a single series.
> >
> > Either way, can you resend the entire series as a V5?
> >
> > Bjorn  
> 
> That's weird.  I can see all 10 got sent. There's something awry with 
> the mailer as I got the copies.  You are right.  Lore only shows 3.  I 
> will see if something happened with the smtp access.  Will resend as V5.

I got all 10.  

May be coincidence but I saw this with a couple of series I was trying
to pick up with b4 (so from lore.kernel.org). I assumed it was a problem
at the sender, but that wasn't intel..

Perhaps something more general going on at vger?

Thanks,

Jonathan

> 
> Thanks,
> 
> Sean


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ