public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
To: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
Cc: Russell King - ARM Linux
	<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
	Kyungmin Park <kmpark-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: omap_apollon_2420_defconfig
Date: Fri, 20 Feb 2009 13:27:06 -0800	[thread overview]
Message-ID: <200902201327.06399.david-b@pacbell.net> (raw)
In-Reply-To: <20090220210644.GE7414-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>

On Friday 20 February 2009, Tony Lindgren wrote:
> * Russell King - ARM Linux <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org> [090220 12:58]:
> > On Tue, Feb 10, 2009 at 10:54:25AM +0900, Kyungmin Park wrote:
> > > In the previous patch, it's only fixed host side. But apollon case, it
> > > only used udc, so udc configuration should select USB_OTG_UTILS also.
> > 
> > So, it's 10 days later, mainline is still broken.  In fact, this is
> > now the only ARM defconfig which is failing.
> > 
> > What's happening?  Is someone going to ack this patch?  Is it going
> > to be submitted to me or is it going to be submitted via some USB
> > tree?
> 
> Well it would be nice to get an ack from the USB people, here's mine:
> 
> Acked-by: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>

I thought this was already handled ... evidently not, so I
just sent it to Greg as a buildfix.


> > Sick of chasing people about build errors.  People here need to get
> > off their lazy backsides, check kautobuild regularly and submit build
> > fixes.

Actually the *standard* practice involves

 (a) bugs getting reported
 (b) patches getting provided
 (c) nagging until the patches merge

I can't fault anyone for sticking to that process and not
going out of their way to seek out kautobuild issues;
there's already *way* too much to do.


> How about automatic notifications on the failing omap builds sent to
> to linux-omap list? The 34xx builds failing because of the compiler
> should be filtered out until the compiler is updated though.

That's a much better solution.  I'd suggest no more than
one such nag message a week though.


> 
> Tony
> 
> 



--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2009-02-20 21:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 19:26 omap_apollon_2420_defconfig Russell King - ARM Linux
2009-02-09 20:53 ` omap_apollon_2420_defconfig Tony Lindgren
     [not found]   ` <20090209205319.GH14200-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2009-02-10  1:54     ` omap_apollon_2420_defconfig Kyungmin Park
2009-02-12  6:31       ` omap_apollon_2420_defconfig David Brownell
     [not found]       ` <9c9fda240902091754q7f723bf2ha46206e52641297b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-02-20 20:58         ` omap_apollon_2420_defconfig Russell King - ARM Linux
2009-02-20 21:06           ` omap_apollon_2420_defconfig Tony Lindgren
     [not found]             ` <20090220210644.GE7414-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2009-02-20 21:24               ` omap_apollon_2420_defconfig Russell King - ARM Linux
2009-02-20 21:40                 ` omap_apollon_2420_defconfig Tony Lindgren
2009-02-20 21:27               ` David Brownell [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=200902201327.06399.david-b@pacbell.net \
    --to=david-b-ybekhbn/0ldr7s880joybq@public.gmane.org \
    --cc=dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=kmpark-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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