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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 15 Apr 2019 07:57:11 -0500
From:   "Gustavo A. R. Silva" <gustavo@...eddedor.com>
To:     Miquel Raynal <miquel.raynal@...tlin.com>
Cc:     David Woodhouse <dwmw2@...radead.org>,
        Brian Norris <computersforpeace@...il.com>,
        Boris Brezillon <bbrezillon@...nel.org>,
        Marek Vasut <marek.vasut@...il.com>,
        Richard Weinberger <richard@....at>,
        linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org,
        Kees Cook <keescook@...omium.org>
Subject: Re: [PATCH] mtd: cfi_util: mark expected switch fall-throughs

Hi Miquel,

On 4/15/19 3:44 AM, Miquel Raynal wrote:
> Hi Gustavo,
> 
> "Gustavo A. R. Silva" <gustavo@...eddedor.com> wrote on Wed, 10 Apr
> 2019 16:16:51 -0500:
> 
>> Hi all,
>>
>> If no one cares I'll add this to my tree for 5.2.
> 
> Which tree are you talking about?
> 

This one:

https://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git/log/?h=for-next/kspp

> Please let the MTD maintainers take patches through their tree. We
> might be late but this is definitely not a good reason to bypass us.
> 
It's a bit confusing when patches are being ignored for more than two
months:

https://lore.kernel.org/patchwork/patch/1040099/
https://lore.kernel.org/patchwork/patch/1040100/
https://lore.kernel.org/patchwork/patch/1040098/

Certainly, Richard Weinberger replied to this one. But I couldn't
find a tree to which this patch was applied, in case it actually
was.

It's a common practice for maintainers to reply saying that a patch
has been finally applied, and in most cases they also explicitly
mention the tree and branch to which it was applied. All this info
is really helpful for people working all over the tree.

I'm only taking this type of patches in my tree when they are being
ignored for a considerable amount of time and even after pinging the
maintainers.

Thanks
--
Gustavo



Powered by blists - more mailing lists