From: Greg KH <gregkh@linuxfoundation.org>
To: James Hogan <james.hogan@imgtec.com>
Cc: jslaby@suse.com, paul.gortmaker@windriver.com, stable@vger.kernel.org
Subject: Re: patch "ttyFDC: Fix build problems due to use of module_{init,exit}" added to tty-next
Date: Mon, 19 Oct 2015 08:11:52 -0700 [thread overview]
Message-ID: <20151019151152.GC20364@kroah.com> (raw)
In-Reply-To: <20151019095917.GE30360@jhogan-linux.le.imgtec.org>
On Mon, Oct 19, 2015 at 10:59:17AM +0100, James Hogan wrote:
> Hi Greg,
>
> On Sun, Oct 18, 2015 at 09:07:52AM -0700, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > ttyFDC: Fix build problems due to use of module_{init,exit}
> >
> > to my tty git tree which can be found at
> > git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git
> > in the tty-next branch.
> >
> > The patch will show up in the next release of the linux-next tree
> > (usually sometime within the next 24 hours during the week.)
> >
> > The patch will also be merged in the next major kernel release
> > during the merge window.
>
> Any chance of applying patch 1 (MIPS: CDMM: Add
> builtin_mips_cdmm_driver() macro) before this one? This patch needs it
> for the definition of the builtin_mips_cdmm_driver macro.
I don't see "patch 1" here, sorry, and my tree can't be rebased :(
greg k-h
next prev parent reply other threads:[~2015-10-19 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 16:07 patch "ttyFDC: Fix build problems due to use of module_{init,exit}" added to tty-next gregkh
2015-10-19 9:59 ` James Hogan
2015-10-19 15:11 ` Greg KH [this message]
2015-10-19 15:28 ` James Hogan
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=20151019151152.GC20364@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=james.hogan@imgtec.com \
--cc=jslaby@suse.com \
--cc=paul.gortmaker@windriver.com \
--cc=stable@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 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.