stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alexandru Moise <00moses.alexander00@gmail.com>
Cc: Harsh 'Shandilya <harsh@prjkt.io>,
	stable@vger.kernel.org, axboe@kernel.dk
Subject: Re: [PATCH v2] block: don't use blocking queue entered for recursive bio submits
Date: Wed, 4 Jul 2018 13:57:45 +0200	[thread overview]
Message-ID: <20180704115745.GA3837@kroah.com> (raw)
In-Reply-To: <20180704114448.GA7545@gmail.com>

On Wed, Jul 04, 2018 at 01:44:48PM +0200, Alexandru Moise wrote:
> On Wed, Jul 04, 2018 at 01:31:54PM +0200, Greg KH wrote:
> > On Wed, Jul 04, 2018 at 04:29:09PM +0530, Harsh 'Shandilya wrote:
> > > On 4 July 2018 3:25:06 PM IST, Alexandru Moise <00moses.alexander00@gmail.com> wrote:
> > > >On Wed, Jul 04, 2018 at 11:16:44AM +0200, Greg KH wrote:
> > > >> On Tue, Jul 03, 2018 at 11:44:53PM +0200, Alexandru Moise wrote:
> > > >> > commit cd4a4ae4683dc2e09380118e205e057896dcda2b upstream.
> > > >> 
> > > >> Who wrote this patch?  Please keep the correct ownership of
> > > >patches...
> > > >> 
> > > >This is Jenses work, I have absolutely nothing to do with it. I just
> > > >want
> > > >to make sure it reaches 4.17, I tried my best to follow these
> > > >guidelines:
> > > >
> > > >https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> > > >
> > > >I assumed that the first Signed-off is implicitly the author of the
> > > >patch.
> > > >Is there something I am missing? Am I misinterpeting the stable kernel
> > > >rules?
> > > 
> > > If you use git format-patch and git send-email for your patches,
> > > they'll come out looking like
> > > https://www.spinics.net/lists/stable/msg236090.html, which appears to
> > > be the proper format since Greg applied those patches without pointing
> > > out any flaws in the format.
> > 
> > That is correct, you need the first line that says "From:" to show that
> > the patch comes from someone other than you.  Please fix that up and
> > resend.
> Understood, thank you for your patience. I was used to just sending patches,
> with mutt.

mutt works great too, just don't change the author "from:" line :)

      reply	other threads:[~2018-07-04 12:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03 21:44 [PATCH v2] block: don't use blocking queue entered for recursive bio submits Alexandru Moise
2018-07-04  9:16 ` Greg KH
2018-07-04  9:55   ` Alexandru Moise
2018-07-04 10:59     ` Harsh 'Shandilya
2018-07-04 11:31       ` Greg KH
2018-07-04 11:44         ` Alexandru Moise
2018-07-04 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=20180704115745.GA3837@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=00moses.alexander00@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=harsh@prjkt.io \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).