public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] tty: add tty_struct->dev pointer to corresponding device instance
Date: Mon, 16 Aug 2010 08:01:21 -0700	[thread overview]
Message-ID: <20100816150121.GA13392@suse.de> (raw)
In-Reply-To: <AANLkTinRVuP7GWo8mrGTy_DR1gv=od5-FQEEb4KO_YWo@mail.gmail.com>

On Mon, Aug 16, 2010 at 02:57:28PM +0400, Dmitry Eremin-Solenikov wrote:
> Hello,
> 
> On Mon, Aug 9, 2010 at 7:08 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > On Mon, ?9 Aug 2010 18:22:49 +0400
> > Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> wrote:
> >
> >> Some device drivers (mostly tty line disciplines) would like to have way
> >> know a struct device instance corresponding to passed tty_struct. Add
> >> a struct device pointer to struct tty_struct and populate it during
> >> initialize_tty_struct().
> >
> > Acked-by: Alan Cox <alan@linux.intel.com>
> >
> 
> Greg, what about these two patches? Can I expect for them to be pulled
> into your patch queue for 2.6.37?

Yes, I will queue them up to my -next branch soon and will go to Linus
for .37.

thanks,

greg k-h

      reply	other threads:[~2010-08-16 16:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-09 14:22 [PATCH 1/2] tty: add tty_struct->dev pointer to corresponding device instance Dmitry Eremin-Solenikov
2010-08-09 14:22 ` [PATCH 2/2] serport: place serport serio device correctly in the device tree Dmitry Eremin-Solenikov
2010-08-11  3:27   ` Dmitry Torokhov
2010-08-09 15:08 ` [PATCH 1/2] tty: add tty_struct->dev pointer to corresponding device instance Alan Cox
2010-08-16 10:57   ` Dmitry Eremin-Solenikov
2010-08-16 15:01     ` 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=20100816150121.GA13392@suse.de \
    --to=gregkh@suse.de \
    --cc=dbaryshkov@gmail.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