public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dirkjan Bussink <dirkjan.bussink@nedap.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tty: Prevent deadlock in n_gsm driver
Date: Wed, 30 Jan 2013 11:06:55 +0100	[thread overview]
Message-ID: <20130130100655.GA31575@kroah.com> (raw)
In-Reply-To: <E78C7BE9-BB39-409D-B2F9-4DAB81BE9513@nedap.com>

On Wed, Jan 30, 2013 at 10:55:00AM +0100, Dirkjan Bussink wrote:
> 
> On 30 Jan 2013, at 06:12, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> 
> > It doesn't apply cleanly to the linux-next tree, can you refresh this
> > and resend it so that I can apply it?  If you want it backported to the
> > stable kernel releases, we can only do that after it gets into Linus's
> > tree, see the file, Documentation/stable_kernel_rules.txt for details
> > about this.
> 
> I've reapplied the patch to linux-next and submitted it just now. Is there
> anything additionally that needs to be done to merge this back to stable
> after this patch is applied? 

You need to add a "cc: stable@vger.kernel.org" line to the
signed-off-by: area.  I'll do it to the patch when I apply it.

I found the problem, your email client stripped out the trailing spaces
of the patch, which kept it from being applied as it wasn't a valid
patch.  I've edited it by hand this time, but next time please fix your
email client.

thanks,

greg k-h

  reply	other threads:[~2013-01-30 10:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29  8:49 [PATCH] Prevent deadlock in n_gsm driver Dirkjan Bussink
2013-01-30  5:12 ` [PATCH] tty: " Greg Kroah-Hartman
2013-01-30  9:51   ` Dirkjan Bussink
2013-01-30 10:10     ` Greg Kroah-Hartman
2013-01-30 10:46       ` Dirkjan Bussink
2013-01-30  9:55   ` Dirkjan Bussink
2013-01-30 10:06     ` Greg Kroah-Hartman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-01-30 10:44 Dirkjan Bussink
2013-03-02 19:07 Ben Hutchings

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=20130130100655.GA31575@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dirkjan.bussink@nedap.com \
    --cc=linux-kernel@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