From: Borislav Petkov <bp@alien8.de>
To: Ramakrishna Saripalli <rsaripal@amd.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, tglx@linutronix.de,
mingo@redhat.com
Subject: Re: [PATCH 0/5] Introduce support for PSF mitigation
Date: Wed, 7 Apr 2021 16:01:00 +0200 [thread overview]
Message-ID: <20210407140100.GE25319@zn.tnic> (raw)
In-Reply-To: <20210407124948.242399-1-rsaripal@amd.com>
On Wed, Apr 07, 2021 at 07:49:48AM -0500, Ramakrishna Saripalli wrote:
> From: Ramakrishna Saripalli <rk.saripalli@amd.com>
It seems you're new to this kernel development thing.
While you're waiting for your patches to be reviewed
fully and properly, please take the time to read
Documentation/process/submitting-patches.rst and all the others in
Documentation/process/ which explains how this whole game works.
For example:
"Once upon a time, patches used to disappear into the void without
comment, but the development process works more smoothly than that
now. You should receive comments within a week or so; if that does not
happen, make sure that you have sent your patches to the right place.
Wait for a minimum of one week before resubmitting or pinging reviewers
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
- possibly longer during busy times like merge windows."
Feel free to ask questions if something's unclear.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-04-07 14:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 12:49 [PATCH 0/5] Introduce support for PSF mitigation Ramakrishna Saripalli
2021-04-07 14:01 ` Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-06 15:49 Ramakrishna Saripalli
2021-04-06 17:26 ` Borislav Petkov
2021-04-07 22:39 ` Josh Poimboeuf
2021-04-08 14:56 ` Saripalli, RK
2021-04-09 9:07 ` Borislav Petkov
2021-04-09 16:45 ` Josh Poimboeuf
2021-04-09 16:50 ` Saripalli, RK
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=20210407140100.GE25319@zn.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rsaripal@amd.com \
--cc=tglx@linutronix.de \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.