mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Praveenkumar I <quic_ipkumar@quicinc.com>,
	mani@kernel.org, agross@kernel.org, andersson@kernel.org,
	lpieralisi@kernel.org, kw@linux.com, robh@kernel.org,
	bhelgaas@google.com, linux-pci@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: quic_varada@quicinc.com, quic_devipriy@quicinc.com
Subject: Re: [PATCH 0/1] Set may payload size for IPQ9574
Date: Mon, 24 Jul 2023 14:50:17 +0200	[thread overview]
Message-ID: <5f707d2e-f944-d991-2c0d-5ea9d02f7572@linaro.org> (raw)
In-Reply-To: <20230724124711.2346886-1-quic_ipkumar@quicinc.com>

On 24.07.2023 14:47, Praveenkumar I wrote:
> IPQ9574 supports 256 bytes of payload size and setting the max will allow
> to use it when capable partner is connected.
> 
It's not necessary to send a (bogus) cover letter with a single patch.

Please consider using the b4 tool, which takes care of almost all sending-
related complaints:

https://b4.docs.kernel.org/en/latest/index.html

Konrad

  parent reply	other threads:[~2023-07-24 12:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24 12:47 Praveenkumar I
2023-07-24 12:47 ` [PATCH 1/1] PCI: qcom: Add early fixup to set the max " Praveenkumar I
2023-07-24 12:53   ` Konrad Dybcio
2023-07-24 13:08     ` Manivannan Sadhasivam
2023-07-24 14:09       ` Manivannan Sadhasivam
2023-07-25  4:46         ` Praveenkumar I
2023-07-25  6:06           ` Manivannan Sadhasivam
2023-07-26  7:28             ` Praveenkumar I
2023-07-26  9:22             ` Praveenkumar I
2023-07-26 10:49               ` Praveenkumar I
2023-07-24 13:51     ` Praveenkumar I
2023-07-24 12:50 ` Konrad Dybcio [this message]
2023-07-25  4:24   ` [PATCH 0/1] Set may " Praveenkumar I

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5f707d2e-f944-d991-2c0d-5ea9d02f7572@linaro.org \
    --to=konrad.dybcio@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=kw@linux.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=quic_devipriy@quicinc.com \
    --cc=quic_ipkumar@quicinc.com \
    --cc=quic_varada@quicinc.com \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®