From: Greg KH <gregkh@linuxfoundation.org>
To: Kumar Amit Mehta <gmate.amit@gmail.com>
Cc: devel@driverdev.osuosl.org, lisa@xenapiadmin.com,
lidza.louina@gmail.com, kernel-janitors@vger.kernel.org,
josh@joshtriplett.org, linux-kernel@vger.kernel.org,
rashika.kheria@gmail.com, dan.carpenter@oracle.com
Subject: Re: [PATCH] staging: sb105x: b_pci_mp.c: fix for non-member access
Date: Fri, 28 Feb 2014 22:20:40 +0000 [thread overview]
Message-ID: <20140228222040.GA27989@kroah.com> (raw)
In-Reply-To: <1393554063-25823-1-git-send-email-gmate.amit@gmail.com>
On Fri, Feb 28, 2014 at 04:21:03AM +0200, Kumar Amit Mehta wrote:
> 'struct tty_struct’ has no member named ‘low_latency’
This driver is marked BROKEN, and can't even compile, how did you test
this patch?
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Kumar Amit Mehta <gmate.amit@gmail.com>
Cc: devel@driverdev.osuosl.org, lisa@xenapiadmin.com,
lidza.louina@gmail.com, kernel-janitors@vger.kernel.org,
josh@joshtriplett.org, linux-kernel@vger.kernel.org,
rashika.kheria@gmail.com, dan.carpenter@oracle.com
Subject: Re: [PATCH] staging: sb105x: b_pci_mp.c: fix for non-member access
Date: Fri, 28 Feb 2014 14:20:40 -0800 [thread overview]
Message-ID: <20140228222040.GA27989@kroah.com> (raw)
In-Reply-To: <1393554063-25823-1-git-send-email-gmate.amit@gmail.com>
On Fri, Feb 28, 2014 at 04:21:03AM +0200, Kumar Amit Mehta wrote:
> 'struct tty_struct’ has no member named ‘low_latency’
This driver is marked BROKEN, and can't even compile, how did you test
this patch?
next prev parent reply other threads:[~2014-02-28 22:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 2:21 [PATCH] staging: sb105x: b_pci_mp.c: fix for non-member access Kumar Amit Mehta
2014-02-28 2:21 ` Kumar Amit Mehta
2014-02-28 22:20 ` Greg KH [this message]
2014-02-28 22:20 ` Greg KH
2014-02-28 22:24 ` Greg KH
2014-02-28 22:24 ` Greg KH
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=20140228222040.GA27989@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gmate.amit@gmail.com \
--cc=josh@joshtriplett.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=lidza.louina@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lisa@xenapiadmin.com \
--cc=rashika.kheria@gmail.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 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.