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] [thread-next>] [day] [month] [year] [list]
Message-ID: <fa63aa02-6a62-417a-a946-9ecd2d6071e6@quicinc.com>
Date: Thu, 4 Jul 2024 08:57:54 +0800
From: Tengfei Fan <quic_tengfan@...cinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
CC: <andersson@...nel.org>, <konrad.dybcio@...aro.org>, <robh@...nel.org>,
        <krzk+dt@...nel.org>, <conor+dt@...nel.org>, <djakov@...nel.org>,
        <mturquette@...libre.com>, <sboyd@...nel.org>,
        <jassisinghbrar@...il.com>, <herbert@...dor.apana.org.au>,
        <davem@...emloft.net>, <manivannan.sadhasivam@...aro.org>,
        <will@...nel.org>, <joro@...tes.org>, <conor@...nel.org>,
        <tglx@...utronix.de>, <amitk@...nel.org>, <thara.gopinath@...il.com>,
        <linus.walleij@...aro.org>, <wim@...ux-watchdog.org>,
        <linux@...ck-us.net>, <rafael@...nel.org>, <viresh.kumar@...aro.org>,
        <vkoul@...nel.org>, <edumazet@...gle.com>, <kuba@...nel.org>,
        <pabeni@...hat.com>, <mcoquelin.stm32@...il.com>,
        <robimarko@...il.com>, <quic_gurus@...cinc.com>,
        <bartosz.golaszewski@...aro.org>, <kishon@...nel.org>,
        <quic_wcheng@...cinc.com>, <alim.akhtar@...sung.com>,
        <avri.altman@....com>, <bvanassche@....org>, <agross@...nel.org>,
        <gregkh@...uxfoundation.org>, <quic_tdas@...cinc.com>,
        <robin.murphy@....com>, <daniel.lezcano@...aro.org>,
        <rui.zhang@...el.com>, <lukasz.luba@....com>,
        <quic_rjendra@...cinc.com>, <ulf.hansson@...aro.org>,
        <quic_sibis@...cinc.com>, <otto.pflueger@...cue.de>,
        <quic_rohiagar@...cinc.com>, <luca@...tu.xyz>,
        <neil.armstrong@...aro.org>, <abel.vesa@...aro.org>,
        <bhupesh.sharma@...aro.org>, <alexandre.torgue@...s.st.com>,
        <peppe.cavallaro@...com>, <joabreu@...opsys.com>,
        <netdev@...r.kernel.org>, <lpieralisi@...nel.org>, <kw@...ux.com>,
        <bhelgaas@...gle.com>, <ahalaney@...hat.com>,
        <krzysztof.kozlowski@...aro.org>, <u.kleine-koenig@...gutronix.de>,
        <quic_cang@...cinc.com>, <danila@...xyga.com>,
        <quic_nitirawa@...cinc.com>, <mantas@...vices.com>,
        <athierry@...hat.com>, <quic_kbajaj@...cinc.com>,
        <quic_bjorande@...cinc.com>, <quic_msarkar@...cinc.com>,
        <quic_devipriy@...cinc.com>, <quic_tsoni@...cinc.com>,
        <quic_rgottimu@...cinc.com>, <quic_shashim@...cinc.com>,
        <quic_kaushalk@...cinc.com>, <quic_tingweiz@...cinc.com>,
        <quic_aiquny@...cinc.com>, <srinivas.kandagatla@...aro.org>,
        <linux-arm-msm@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <linux-pm@...r.kernel.org>,
        <linux-clk@...r.kernel.org>, <linux-phy@...ts.infradead.org>,
        <linux-crypto@...r.kernel.org>, <linux-scsi@...r.kernel.org>,
        <linux-usb@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
        <iommu@...ts.linux.dev>, <linux-riscv@...ts.infradead.org>,
        <linux-gpio@...r.kernel.org>, <linux-watchdog@...r.kernel.org>,
        <linux-pci@...r.kernel.org>,
        <linux-stm32@...md-mailman.stormreply.com>, <kernel@...cinc.com>
Subject: Re: [PATCH 00/47] arm64: qcom: dts: add QCS9100 support



On 7/3/2024 6:33 PM, Dmitry Baryshkov wrote:
> On Wed, Jul 03, 2024 at 11:56:48AM GMT, Tengfei Fan wrote:
>> Introduce support for the QCS9100 SoC device tree (DTSI) and the
>> QCS9100 RIDE board DTS. The QCS9100 is a variant of the SA8775p.
>> While the QCS9100 platform is still in the early design stage, the
>> QCS9100 RIDE board is identical to the SA8775p RIDE board, except it
>> mounts the QCS9100 SoC instead of the SA8775p SoC.
> 
> Your patch series includes a second copy of your patches, wich have
> different Message-IDs:
> 
> 20240703035735.2182165-1-quic_tengfan@...cinc.com vs
> 20240703025850.2172008-1-quic_tengfan@...cinc.com
> 
> Please consider switching to the b4 tool or just
> checking what is being sent.
> 

This is because I encountered a "Connection timed out" error while 
sending this patch series using "git send-email". I wanted to add 
"--in-reply-to=" git paramater to resend the patches that haven't been 
pushed yet, which resulted in this second copy error result.

I'll following your suggestion and use the b4 tool when sending the new 
version patch series to avoid similar error.

-- 
Thx and BRs,
Tengfei Fan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ