mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Felipe Balbi <balbi@kernel.org>
Cc: Pawel Laszczak <pawell@cadence.com>, Greg KH <greg@kroah.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Roger Quadros <rogerq@ti.com>
Subject: Re: linux-next: build failure after merge of the usb and usb-gadget trees
Date: Thu, 4 Jul 2019 10:53:26 -0500	[thread overview]
Message-ID: <20190704155326.f75xhkpyh5mq4467@kahuna> (raw)
In-Reply-To: <87imsiyzo3.fsf@linux.intel.com>

On 11:25-20190704, Felipe Balbi wrote:
[...]

> This is what I get for trusting people to do their part. I couldn't even
> compile test this since I don't have ARM compilers anymore (actually,
> just installed to test). Your customer, however, uses ARM cores so I
> would expect you to have at least compile tested this on ARM. How come
> this wasn't verified by anybody at TI?

Sorry about that Felipe/Greg, will try and make sure we put in steps so
that this does'nt happen again.

> 
> TI used to have automated testing for many of the important defconfigs,
> is that completely gone? Are you guys relying entirely on linux-next?

We still do. Kind of a unfortunately co-incidence, there has been for a
few weeks a downtime given the test infrastructure has been changing and
the continual automated testing env is down for community kernel. But,
that said, we also did move to focussing on linux-next, which should be
revisited.


-- 
Regards,
Nishanth Menon

  parent reply	other threads:[~2019-07-04 15:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04  6:34 Stephen Rothwell
2019-07-04  6:59 ` Greg KH
2019-07-04  7:28   ` Felipe Balbi
2019-07-04  8:07     ` Pawel Laszczak
2019-07-04  8:25       ` Felipe Balbi
2019-07-04  8:32         ` Greg KH
2019-07-04  8:45           ` Felipe Balbi
2019-07-04 11:03             ` Greg KH
2019-07-04  9:08         ` Pawel Laszczak
2019-07-04  9:25           ` Pawel Laszczak
2019-07-04  9:45             ` Felipe Balbi
2019-07-04  9:44           ` Felipe Balbi
2019-07-04 11:03             ` Greg KH
2019-07-04 11:06               ` Felipe Balbi
2019-07-05  4:42                 ` Pawel Laszczak
2019-07-04 15:53         ` Nishanth Menon [this message]
2019-07-08 15:09         ` Sekhar Nori
2019-07-04  7:47   ` Stephen Rothwell

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=20190704155326.f75xhkpyh5mq4467@kahuna \
    --to=nm@ti.com \
    --cc=balbi@kernel.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=pawell@cadence.com \
    --cc=rogerq@ti.com \
    --cc=sfr@canb.auug.org.au \
    /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

all inboxes | Powered by JetHome®