public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Visweswara Tanuku <quic_vtanuku@quicinc.com>
Cc: konrad.dybcio@linaro.org, bartosz.golaszewski@linaro.org,
	linux-kernel@vger.kernel.org, quic_vnivarth@quicinc.com,
	nicolas.dechesne@linaro.org, srinivas.kandagatla@linaro.org,
	vinod.koul@linaro.org, quic_eberman@quicinc.com,
	quic_satyap@quicinc.com
Subject: Re: [RESEND] soc: qcom-geni-se: Update Tx and Rx fifo depth based on QUP HW version
Date: Wed, 8 Feb 2023 12:57:17 +0100	[thread overview]
Message-ID: <Y+OOHWBzL+GINcLW@kroah.com> (raw)
In-Reply-To: <0afc0752-1a4e-be3a-e9bd-0f56243d5e41@quicinc.com>

On Tue, Feb 07, 2023 at 04:54:13PM +0530, Visweswara Tanuku wrote:
> 
> On 2/6/2023 11:39 PM, Greg KH wrote:
> > A:http://en.wikipedia.org/wiki/Top_post
> > Q: Were do I find info about this thing called top-posting?
> > A: Because it messes up the order in which people normally read text.
> > Q: Why is top-posting such a bad thing?
> > A: Top-posting.
> > Q: What is the most annoying thing in e-mail?
> > 
> > A: No.
> > Q: Should I include quotations after my reply?
> 
> Apologies will take care.
> 
> > http://daringfireball.net/2007/07/on_top
> > 
> > On Mon, Feb 06, 2023 at 07:36:49PM +0530, Visweswara Tanuku wrote:
> > > Added RESEND for resubmission of first version which is not modified in any
> > > way from the previous submission.
> > 
> > Then why was it resent?  What will cause this to be accepted when the
> > previous submission was not?
> > 
> > confused,
> > 
> > greg k-h
> 
> https://lkml.org/lkml/2022/11/21/549
> 
> I had posted the same patch in November last year but did not receive any
> response in spite of periodic reminders.
> 
> Suspecting that the patch did not reach all the required recipients
> re-posted the same and hence RESEND.

When you resend, you need to say _why_ it was resent.  "adding more
people" is a valid reason, don't make us guess.

Remember, some of us get hundreds of patches a day/week to review, we
have no saved context.

thanks,

greg k-h

      parent reply	other threads:[~2023-02-08 11:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 12:22 [RESEND] soc: qcom-geni-se: Update Tx and Rx fifo depth based on QUP HW version Visweswara Tanuku
2023-02-06 12:38 ` Greg KH
     [not found]   ` <ca31f247-0297-7582-c16f-a85453872ca4@quicinc.com>
2023-02-06 18:09     ` Greg KH
     [not found]       ` <0afc0752-1a4e-be3a-e9bd-0f56243d5e41@quicinc.com>
2023-02-08 11:57         ` Greg KH [this message]

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=Y+OOHWBzL+GINcLW@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.dechesne@linaro.org \
    --cc=quic_eberman@quicinc.com \
    --cc=quic_satyap@quicinc.com \
    --cc=quic_vnivarth@quicinc.com \
    --cc=quic_vtanuku@quicinc.com \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=vinod.koul@linaro.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