Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: "Watkins, Melissa" <m-watkins@ti.com>,
	Melissa Watkins <mwatkins.ti@gmail.com>
Subject: Re: [PATCH 6/6] defconfig: Add omapl138 defconfig file
Date: Tue, 07 Dec 2010 14:12:38 -0500	[thread overview]
Message-ID: <20101207191238.GB6510@denix.org> (raw)
In-Reply-To: <131E5DFBE7373E4C8D813795A6AA7F080329CC1EDC@dlee06.ent.ti.com>

Melissa,

I would suggest that you actually subscribe to this mailing list, so your 
patches can get through and people can review them (although Koen has already 
applied them).

-- 
Denys


On Fri, Dec 03, 2010 at 01:43:28PM -0600, Maupin, Chase wrote:
> My main comment here is that these patches might be better in a different 
> order.  Currently if they were applied one at a time they would fail because 
> of the dependency order.  I would suggest re-ordering the existing patches 
> into the following order:
> 
> 0005
> 0006
> 0004
> 0003
> 0002
> 0001
> 
> Sorry that I didn't notice this the first time I looked at these patches.
> 
> > -----Original Message-----
> > From: Melissa Watkins [mailto:mwatkins.ti@gmail.com]
> > Sent: Friday, December 03, 2010 9:41 AM
> > To: openembedded-devel@lists.openembedded.org
> > Cc: Watkins, Melissa; Maupin, Chase
> > Subject: [PATCH 6/6] defconfig: Add omapl138 defconfig file
> > 
> > * Add defconfig file for omapl138 machines
> > 
> > Signed-off-by: Melissa Watkins <m-watkins@ti.com>
> > Signed-off-by: Chase Maupin <chase.maupin@ti.com>
> > ---
> >  recipes/linux/linux-davinci/omapl138/defconfig |    8 +++++++-
> >  1 files changed, 7 insertions(+), 1 deletions(-)
> > 
> > diff --git a/recipes/linux/linux-davinci/omapl138/defconfig
> > b/recipes/linux/linux-davinci/omapl138/defconfig
> > index 8462139..ad52484 100644
> > --- a/recipes/linux/linux-davinci/omapl138/defconfig
> > +++ b/recipes/linux/linux-davinci/omapl138/defconfig
> > @@ -1383,6 +1383,7 @@ CONFIG_USB_MUSB_HDRC=y
> >  CONFIG_USB_MUSB_SOC=y
> >  CONFIG_USB_MUSB_HOST=y
> >  # CONFIG_USB_MUSB_PERIPHERAL is not set
> > +# CONFIG_USB_MUSB_DUAL_ROLE is not set
> >  # CONFIG_USB_MUSB_OTG is not set
> >  CONFIG_USB_MUSB_HDRC_HCD=y
> >  # CONFIG_MUSB_PIO_ONLY is not set
> > @@ -1557,7 +1558,12 @@ CONFIG_RTC_INTF_DEV=y
> >  CONFIG_RTC_DRV_OMAP=y
> >  # CONFIG_DMADEVICES is not set
> >  # CONFIG_AUXDISPLAY is not set
> > -# CONFIG_UIO is not set
> > +CONFIG_UIO=y
> > +# CONFIG_UIO_PDRV is not set
> > +# CONFIG_UIO_PDRV_GENIRQ is not set
> > +# CONFIG_UIO_SMX is not set
> > +# CONFIG_UIO_SERCOS3 is not set
> > +CONFIG_UIO_PRUSS=m
> > 
> >  #
> >  # TI VLYNQ
> > --
> > 1.7.0.4
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



      parent reply	other threads:[~2010-12-07 19:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1291390869-14422-1-git-send-email-m-watkins@ti.com>
2010-12-03 19:43 ` [PATCH 6/6] defconfig: Add omapl138 defconfig file Maupin, Chase
2010-12-04 12:23   ` Koen Kooi
2010-12-07 19:12   ` Denys Dmytriyenko [this message]

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=20101207191238.GB6510@denix.org \
    --to=denis@denix.org \
    --cc=m-watkins@ti.com \
    --cc=mwatkins.ti@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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