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: <20230313222123.fshj3vvpbpcptyru@mobilestation>
Date:   Tue, 14 Mar 2023 01:21:23 +0300
From:   Serge Semin <fancer.lancer@...il.com>
To:     Bjorn Helgaas <helgaas@...nel.org>
Cc:     Serge Semin <Sergey.Semin@...kalelectronics.ru>,
        Bjorn Helgaas <bhelgaas@...gle.com>,
        Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
        Cai Huoqing <cai.huoqing@...ux.dev>,
        Jingoo Han <jingoohan1@...il.com>,
        Gustavo Pimentel <gustavo.pimentel@...opsys.com>,
        Vinod Koul <vkoul@...nel.org>,
        Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
        Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>,
        Rob Herring <robh@...nel.org>,
        Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>,
        Pavel Parkhomenko <Pavel.Parkhomenko@...kalelectronics.ru>,
        linux-pci@...r.kernel.org, dmaengine@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND v2 00/11] PCI: dwc: Relatively simple fixes and
 cleanups

Hi Bjorn

On Mon, Mar 13, 2023 at 04:17:52PM -0500, Bjorn Helgaas wrote:
> On Mon, Mar 13, 2023 at 11:08:04PM +0300, Serge Semin wrote:
> > ...
> > Link: https://lore.kernel.org/linux-pci/20230217093956.27126-1-Sergey.Semin@baikalelectronics.ru/
> > Changelog v2:
> > - Rebase onto the kernel 6.3-rc2.
> 

> This is fine, but just FYI that there's no need to rebase past -rc1
> because PCI patches are applied on topic branches based on the PCI
> "main" branch, typically -rc1.

Thanks for reminding about that. I am not that keen of early rc's
because there is a higher risk to catch instability in unexpected
places. Normally I wait for rc2 or newer kernel is released in order
to rebase onto that mainline kernel. I am using the Linus' master
because most of time I get to develop and submit patchsets for several
subsystems concurrently (currently it's PCIe, EDAC, net and MIPS-arch)
and having them rebased on top of each subsystem' next-branch would be
even more risky. Of course I understand that the subsystem main/topic
branches may have some conflicting changes. So normally I make sure
that the submitted changes are applicable against the subsystem trees
if/when it's necessary. (Can't deny though I forget to do that from
time to time.)

-Serge(y)

> 
> Bjorn

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ