[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8A71B368A89016469F72CD08050AD3340C527BB9@maui.asicdesigners.com>
Date: Wed, 3 Oct 2012 19:12:38 -0700
From: "Jay Hernandez" <jay@...lsio.com>
To: "David Miller" <davem@...emloft.net>, <sfr@...b.auug.org.au>
Cc: <netdev@...r.kernel.org>, <linux-next@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, "Vipul Pandya" <vipul@...lsio.com>,
"Jay Hernandez" <jay@...lsio.com>
Subject: RE: linux-next: build failure after merge of the net tree
David and Stephen,
I apologize for not taking the necessary steps to verify our patches
before submission. Ignorance is not an excuse... Anyways David thank you
for fixing the issue for us.
Jay-
-----Original Message-----
From: David Miller [mailto:davem@...emloft.net]
Sent: Wednesday, October 03, 2012 6:48 PM
To: sfr@...b.auug.org.au
Cc: netdev@...r.kernel.org; linux-next@...r.kernel.org;
linux-kernel@...r.kernel.org; Vipul Pandya; Jay Hernandez
Subject: Re: linux-next: build failure after merge of the net tree
From: Stephen Rothwell <sfr@...b.auug.org.au>
Date: Thu, 4 Oct 2012 11:06:15 +1000
> Actually, for me it is. I have a script that does the "use
> yesterday's version" for me. To fix (even a one liner) means bringing
> up an editor, commiting, creating the patch and then recommiting it
> (an implementation
> detail) and recording that I need to keep (automatically) applying the
> patch in case the maintainer doesn't react quickly.
Ok, fair enough.
I'll try to look into making x86 barf when a vmalloc.h include is
missing.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists