From: Greg KH <gregkh@linuxfoundation.org>
To: Tigran Aivazian <aivazian.tigran@gmail.com>
Cc: torvalds@linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [patch set 4.19.6] BFS updates
Date: Mon, 3 Dec 2018 11:26:31 +0100 [thread overview]
Message-ID: <20181203102631.GA18219@kroah.com> (raw)
In-Reply-To: <CAK+_RLmJTrc3P0q0rzjoo4LD=g2cyA0eRwoVUtg-V8kPYEg7eg@mail.gmail.com>
On Mon, Dec 03, 2018 at 09:55:23AM +0000, Tigran Aivazian wrote:
> Re-sending the patches with the "Cc: stable@vger.kernel.org" included
> in the sign-off area, as per Option 1 of the rules Greg referred me
> to. I hope that now I have done everything by the rules.
As you want to replace an existing patch in linux-next that is in
Andrew's trees, you need to cc: him :)
Also, you need to send each patch as an individual email, like
Documentation/SubmittingPatches says to do.
This shouldn't be any different from submitting any other patch.
thanks,
greg k-h
prev parent reply other threads:[~2018-12-03 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-02 21:01 [patch set 4.19.6] BFS updates Tigran Aivazian
2018-12-02 21:42 ` Tigran Aivazian
2018-12-03 9:55 ` Tigran Aivazian
2018-12-03 10:26 ` 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=20181203102631.GA18219@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aivazian.tigran@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).