From: Amit Shah <amit.shah@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org, Milton Miller <miltonm@bga.com>,
linuxppc-dev@ozlabs.org
Subject: Re: hvc_console: Don't access hvc_task if not initialised
Date: Thu, 28 Apr 2011 09:30:00 +0530 [thread overview]
Message-ID: <20110428040000.GA16167@amit-x200.redhat.com> (raw)
In-Reply-To: <20110428000934.GA14294@kroah.com>
On (Wed) 27 Apr 2011 [17:09:34], Greg KH wrote:
> On Wed, Apr 27, 2011 at 12:01:47PM +0530, Amit Shah wrote:
> > On (Wed) 27 Apr 2011 [14:31:29], Rusty Russell wrote:
> > > On Wed, 20 Apr 2011 22:36:10 +0530, Amit Shah <amit.shah@redhat.com> wrote:
> > > > On (Wed) 20 Apr 2011 [07:34:35], Greg KH wrote:
> > > > > Care to either create this patch, or resend your original one, if you
> > > > > want it applied?
> > > >
> > > > Rusty has the other one queued. I pinged him about status.
> > >
> > > It's merged, but I don't think it had the requisite cc:stable, did it?
> >
> > No, because at the point of submitting I didn't know it would solve
> > this bug as well. Greg, can you pick
> > afa2689e19073cd2e762d0f2c1358fab1ab9f18c for stable?
>
> Yes, but in the future, this is NOT the way to get patches into the
> stable tree. Please read Documentation/stable_kernel_rules.txt for how
> to do it properly.
Got it, thanks!
Amit
prev parent reply other threads:[~2011-04-28 4:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 7:29 [PATCH] hvc_console: Don't access hvc_task if not initialised Amit Shah
2011-03-24 14:58 ` Milton Miller
2011-03-25 8:47 ` Amit Shah
2011-03-28 17:52 ` Milton Miller
2011-04-20 12:33 ` Amit Shah
2011-04-20 14:34 ` Greg KH
2011-04-20 17:06 ` Amit Shah
2011-04-27 5:01 ` Rusty Russell
2011-04-27 6:31 ` Amit Shah
2011-04-28 0:09 ` Greg KH
2011-04-28 4:00 ` Amit Shah [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=20110428040000.GA16167@amit-x200.redhat.com \
--to=amit.shah@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=miltonm@bga.com \
--cc=rusty@rustcorp.com.au \
/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).