All of lore.kernel.org
 help / color / mirror / Atom feed
From: lists@kaiser.cx (Martin Kaiser)
To: kernelnewbies@lists.kernelnewbies.org
Subject: submitting a patch for a stable tree
Date: Mon, 18 Dec 2017 13:54:04 +0100	[thread overview]
Message-ID: <20171218125404.GA17813@botnar.kaiser.cx> (raw)
In-Reply-To: <20171217202345.GA23734@kroah.com>

Hello Greg,

Thus wrote Greg KH (greg at kroah.com):

> You did?  Was this on December 12:
> 	Subject: [PATCH] mfd: fsl-imx25: Clean up irq settings during removal
> ?

yes, that was what I submitted.

> If so, I totally missed it (just now dug in my archives to find it.)

> > Is there anything that's wrong or missing? Is there a mailing list
> > archive for stable at vger.kernel.org where I can have a look at correct
> > submissions and check that my submission made it to the list?

> There is an archive, yes, I think vger lists it.

The gmane.org achive listed there doesn't work. Someone added a link to
the spinics.net archive recently, this is working.

> As for what to do next time, I ignored this as I didn't know what to do
> with it.  For some reason I thought it was just a "normal" patch being
> sent to the subsystem, sorry.

> Next time put below the --- line something like "Can you queue this up
> for 4.14?"

Ok, understood. I'll do that next time.

> Or even a simpler email would be:
> 	Can you please include git commit id 18f773937968 ("mfd:
> 	fsl-imx25: Clean up irq settings during removal") in the 4.14
> 	stable tree?  I forgot to tag it when I submitted it to the mfd
> 	subsystem.

> And I can take it from there.

> Care to try that?

Sure. But you beat me to it and queued the patch already ;-)

> And also, you can just email the stable list in response to your
> original message saying "Just curious as to the state of this."  I do
> get a ton of email, and sometimes things fall through the cracks, like
> this time.  Being reminded after a week or two is not a problem, if you
> don't get a response, it's usually required :)

Ok, just wanted to check first if I submitted the patch correctly.

Anyway, thanks for the quick repsonse and for queuing the patch.

   Martin

      parent reply	other threads:[~2017-12-18 12:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-17 19:24 submitting a patch for a stable tree Martin Kaiser
2017-12-17 20:23 ` Greg KH
2017-12-18  9:38   ` Greg KH
2017-12-18 13:04     ` Martin Kaiser
2017-12-18 12:54   ` Martin Kaiser [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=20171218125404.GA17813@botnar.kaiser.cx \
    --to=lists@kaiser.cx \
    --cc=kernelnewbies@lists.kernelnewbies.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.