All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Lee Howard <lee.howard@mainpine.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: Mainpine IQ Express Rev3 problems beginning 2.6.36
Date: Mon, 10 Jan 2011 16:02:31 -0800	[thread overview]
Message-ID: <20110111000231.GA30424@kroah.com> (raw)
In-Reply-To: <64E919E148714BFCB46D62A05E9EF13D@callisto>

On Fri, Dec 17, 2010 at 05:25:19AM -0800, Lee Howard wrote:
> > -----Original Message-----
> > From: linux-serial-owner@vger.kernel.org 
> > [mailto:linux-serial-owner@vger.kernel.org] On Behalf Of Lee Howard
> > Sent: Tuesday, December 14, 2010 11:50 AM
> > To: 'Greg KH'
> > Cc: linux-serial@vger.kernel.org
> > Subject: RE: Mainpine IQ Express Rev3 problems beginning 2.6.36
> > 
> > > -----Original Message-----
> > > From: Greg KH [mailto:greg@kroah.com]
> > > Sent: Sunday, December 12, 2010 8:52 AM
> > 
> > > As for build issues, try to make a minimal working config for your 
> > > system, using 'make localmodconfig'.  That will speed up your build 
> > > time immensely as well as reduce your chances of build and runtime 
> > > problems with the intermediate kernels.
> > 
> > Thank-you, that did help immensely.
> > 
> > Here's the 'git bisect' result...
> > 
> > --------------
> > 7a56aa45982bb87bfca98a2832b5ae782c03364a is the first bad 
> > commit commit 7a56aa45982bb87bfca98a2832b5ae782c03364a
> > Author: Yegor Yefremov <yegor_sub1@visionsystems.de>
> > Date:   Wed Jun 16 16:29:55 2010 +0200
> > 
> >     serial: add UART_CAP_EFR and UART_CAP_SLEEP flags to 
> > 16C950 UARTs definition
> >     
> >     Adding UART_CAP_EFR and UART_CAP_SLEEP flags will enable 
> > sleep mode
> >     and automatic CTS flow control for 16C950 UARTs. It will 
> > also avoid
> >     capabilities detection warning like this:
> >     
> >     "ttyS0: detected caps 00000700 should be 00000100"
> >     
> >     Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> >     Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> > 
> > :040000 040000 1776ca8d5c653834363c0778b5b404ee52bd2d69
> > b81cfe4f302a674935181bd248641873820517e5 M      drivers
> > --------------
> > 
> > Indeed, if I remove the UART_CAP_EFR flag from later kernel 
> > revisions there is no problem.
> 
> Greg,
> 
> What's to be done?

Sorry for the delay, I think Pavel's posted patch will solve this issue
for you, right?

thanks,

greg k-h

  reply	other threads:[~2011-01-11  0:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 23:55 Mainpine IQ Express Rev3 problems beginning 2.6.36 Lee Howard
2010-12-09  6:42 ` Greg KH
2010-12-12  0:36   ` Lee Howard
2010-12-12 16:52     ` Greg KH
2010-12-14 19:49       ` Lee Howard
2010-12-17 13:25         ` Lee Howard
2011-01-11  0:02           ` Greg KH [this message]
2011-01-11 19:16             ` Lee Howard
2011-01-11 23:03               ` Greg KH
2011-01-25 15:57                 ` Lee Howard

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=20110111000231.GA30424@kroah.com \
    --to=greg@kroah.com \
    --cc=lee.howard@mainpine.com \
    --cc=linux-serial@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.