public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Puma Hsu <pumahsu@google.com>
Cc: Oliver Neukum <oneukum@suse.com>,
	mka@chromium.org, dianders@chromium.org, albertccwang@google.com,
	raychi@google.com, howardyen@google.com, leejj@google.com,
	hch@infradead.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] add hooks for usb suspend and resume
Date: Fri, 23 Dec 2022 15:52:00 +0100	[thread overview]
Message-ID: <Y6XAkF5MyfW6XNzV@kroah.com> (raw)
In-Reply-To: <CAGCq0LZ6PLF+CCOAU6LSr3DaZ78MQ3kAmKwnXPEtjC76GsRPUg@mail.gmail.com>

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?

http://daringfireball.net/2007/07/on_top

On Fri, Dec 23, 2022 at 11:00:00AM +0800, Puma Hsu wrote:
> Thanks for the comments. I will have an introduction for our design first.

<snip>

Please put this in the next round of patches you all submit, and work
together to NOT submit independant patch series when they are obviously
interconnected.

thanks,

greg k-h

      parent reply	other threads:[~2022-12-23 14:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14  8:14 [PATCH v2 0/2] add hooks for usb suspend and resume Puma Hsu
2022-12-14  8:14 ` [PATCH v2 1/2] usb: core: " Puma Hsu
2022-12-14  8:14 ` [PATCH v2 2/2] usb: core: add implementations for usb suspend/resume hooks Puma Hsu
2022-12-14  8:57   ` Christoph Hellwig
2022-12-14  8:48 ` [PATCH v2 0/2] add hooks for usb suspend and resume Greg KH
2022-12-14  9:17 ` Oliver Neukum
     [not found]   ` <CAGCq0LZ6PLF+CCOAU6LSr3DaZ78MQ3kAmKwnXPEtjC76GsRPUg@mail.gmail.com>
2022-12-23 14:52     ` 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=Y6XAkF5MyfW6XNzV@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=albertccwang@google.com \
    --cc=dianders@chromium.org \
    --cc=hch@infradead.org \
    --cc=howardyen@google.com \
    --cc=leejj@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=oneukum@suse.com \
    --cc=pumahsu@google.com \
    --cc=raychi@google.com \
    /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