From: Greg KH <gregkh@linuxfoundation.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: "Justin P. Mattock" <justinmattock@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH]NEXT:drivers:staging:ramster Fix typos and remove CONFIG_BROKEN in staging:ramster
Date: Thu, 12 Apr 2012 12:17:55 -0700 [thread overview]
Message-ID: <20120412191755.GD22154@kroah.com> (raw)
In-Reply-To: <8f7aee45-fc5c-43b2-97cc-30c142927dc3@default>
On Thu, Apr 12, 2012 at 09:50:38AM -0700, Dan Magenheimer wrote:
> > From: Justin P. Mattock [mailto:justinmattock@gmail.com]
> > Sent: Monday, April 09, 2012 8:49 AM
> > To: dan.magenheimer@oracle.com
> > Cc: linux-kernel@vger.kernel.org; gregkh@linuxfoundation.org; Justin P. Mattock
> > Subject: [PATCH]NEXT:drivers:staging:ramster Fix typos and remove CONFIG_BROKEN in staging:ramster
> >
> > From: "Justin P. Mattock" <justinmattock@gmail.com>
> >
> > The below patch fixes some typos that I found while reading. And also removes
> > CONFIG_BROKEN since it is no longer used.
> >
> > Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>
>
> Hi Justin --
>
> Thanks for your interest and for the patch!
>
> The removal of CONFIG_BROKEN is already in GregKH's staging tree(s)
> and in linux-next, and will hopefully be in -rc3.
>
> The comment typos do need to be fixed but I'm not sure if they should
> go through the staging tree or through trivial, but in either case
> consider them:
I already took them into my tree, and took out the CONFIG_BROKEN part of
this patch, so all is good :)
greg k-h
next prev parent reply other threads:[~2012-04-12 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<1333982937-12929-1-git-send-email-user@Ideapad-Z560>
2012-04-12 16:50 ` [PATCH]NEXT:drivers:staging:ramster Fix typos and remove CONFIG_BROKEN in staging:ramster Dan Magenheimer
2012-04-12 18:04 ` Justin P. Mattock
2012-04-12 19:17 ` Greg KH [this message]
2012-04-09 14:48 Justin P. Mattock
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=20120412191755.GD22154@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dan.magenheimer@oracle.com \
--cc=justinmattock@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