From: Greg KH <greg@kroah.com>
To: Timur Tabi <timur@freescale.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
linux-console@vger.kernel.org
Subject: Re: [PATCH] drivers/tty: don't use the byte channel handle as a parameter in ehv_bytechan.c
Date: Thu, 22 Sep 2011 16:28:28 -0700 [thread overview]
Message-ID: <20110922232828.GA12088@kroah.com> (raw)
In-Reply-To: <4E7BC1A9.5050708@freescale.com>
On Thu, Sep 22, 2011 at 06:15:53PM -0500, Timur Tabi wrote:
> Greg KH wrote:
> > This patch doesn't apply at all to my tty tree, what was it made
> > against?
>
> An internal repository that supposed to be in-sync with the latest and greatest.
>
> What's the URL for your tty-next repo?
There is no public one due to kernel.org being down.
Does your patch apply to linux-next?
next prev parent reply other threads:[~2011-09-22 23:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 18:26 [PATCH] drivers/tty: don't use the byte channel handle as a parameter in ehv_bytechan.c Timur Tabi
2011-09-22 23:06 ` Greg KH
2011-09-22 23:15 ` Timur Tabi
2011-09-22 23:28 ` Greg KH [this message]
2011-09-23 1:11 ` Tabi Timur-B04825
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=20110922232828.GA12088@kroah.com \
--to=greg@kroah.com \
--cc=linux-console@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@freescale.com \
/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