workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bird, Tim" <Tim.Bird@sony.com>
To: Greg KroahHartman <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>,
	"corbet@lwn.net" <corbet@lwn.net>,
	"workflows@vger.kernel.org" <workflows@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] docs: stable-kernel-rules: fix typo sent->send
Date: Tue, 30 Apr 2024 18:12:11 +0000	[thread overview]
Message-ID: <SA3PR13MB63720647D48D0D725539549EFD1A2@SA3PR13MB6372.namprd13.prod.outlook.com> (raw)
In-Reply-To: <2024042715-repossess-unshackle-a078@gregkh>

Thanks.  I realize I should not have copied stable@kernel.org on this.
typo fixes are out-of-policy for stable.  Sorry for the noise.
 -- Tim

> -----Original Message-----
> From: Greg KroahHartman <gregkh@linuxfoundation.org>
> Sent: Saturday, April 27, 2024 4:10 AM
> To: Bird, Tim <Tim.Bird@sony.com>
> Cc: Sasha Levin <sashal@kernel.org>; corbet@lwn.net; stable@vger.kernel.org; workflows@vger.kernel.org; linux-doc@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] docs: stable-kernel-rules: fix typo sent->send
> 
> On Fri, Apr 26, 2024 at 11: 18: 14PM +0000, Bird, Tim wrote: > > Change 'sent' to 'send' > > Signed-off-by: Tim Bird <tim. bird@ sony. com> > ---
> > Documentation/process/stable-kernel-rules. rst | 2 +- > 1 file changed,
> 
> On Fri, Apr 26, 2024 at 11:18:14PM +0000, Bird, Tim wrote:
> >
> > Change 'sent' to 'send'
> >
> > Signed-off-by: Tim Bird <tim.bird@sony.com>
> > ---
> >  Documentation/process/stable-kernel-rules.rst | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst
> > index 1704f1c686d0..3178bef6fca3 100644
> > --- a/Documentation/process/stable-kernel-rules.rst
> > +++ b/Documentation/process/stable-kernel-rules.rst
> > @@ -78,7 +78,7 @@ in the sign-off area. Once the patch is mainlined it will be applied to the
> >  stable tree without anything else needing to be done by the author or
> >  subsystem maintainer.
> >
> > -To sent additional instructions to the stable team, use a shell-style inline
> > +To send additional instructions to the stable team, use a shell-style inline
> >  comment:
> >
> >   * To specify any additional patch prerequisites for cherry picking use the
> > --
> > 2.25.1
> >
> >
> 
> Thanks for this.  If Jon wants to pick this up:
> 
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> 
> is fine from me, or I can take it through my tree as well.
> 
> thanks,
> 
> greg k-h

  reply	other threads:[~2024-04-30 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26 23:18 Bird, Tim
2024-04-27 10:09 ` Greg KroahHartman
2024-04-30 18:12   ` Bird, Tim [this message]
2024-04-27 10:25 ` Bagas Sanjaya
2024-05-02 16:21 ` Jonathan Corbet

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=SA3PR13MB63720647D48D0D725539549EFD1A2@SA3PR13MB6372.namprd13.prod.outlook.com \
    --to=tim.bird@sony.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=workflows@vger.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