[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140408161054.GA26210@e106331-lin.cambridge.arm.com>
Date: Tue, 8 Apr 2014 17:10:54 +0100
From: Mark Rutland <mark.rutland@....com>
To: Borislav Petkov <bp@...en8.de>
Cc: Thor Thayer <tthayer@...era.com>,
"robherring2@...il.com" <robherring2@...il.com>,
"dougthompson@...ssion.com" <dougthompson@...ssion.com>,
"grant.likely@...aro.org" <grant.likely@...aro.org>,
Pawel Moll <Pawel.Moll@....com>,
"ijc+devicetree@...lion.org.uk" <ijc+devicetree@...lion.org.uk>,
"galak@...eaurora.org" <galak@...eaurora.org>,
"rob@...dley.net" <rob@...dley.net>,
"linux@....linux.org.uk" <linux@....linux.org.uk>,
"dinguyen@...era.com" <dinguyen@...era.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/3] edac: altera: Add SDRAM EDAC support for
CycloneV/ArriaV
On Tue, Apr 08, 2014 at 05:03:51PM +0100, Borislav Petkov wrote:
> On Tue, Apr 08, 2014 at 04:40:17PM +0100, Mark Rutland wrote:
> > The patches should be in the same series, but for review purposes it's
> > nicer if the bindings are separate patches from the code within that
> > series.
> >
> > I usually look at the drivers implementing bindings and prefer to be
> > Cc'd on the whole series, with both the binding and driver.
>
> Right, but I got only the 3/3 patch on linux-edac which made me wonder.
Ah. The whole series should've been Cc'd to linux-edac; I didn't realise
that wasn't the case.
> So I'm guessing you or someone else would be picking the whole set once
> I've acked the EDAC part?
Typically the bindings would go with the driver via the appropriate
subsystem maintainer. That way we don't get bindings without drivers or
vice-versa if there's a problem part-way, and we don't end up with every
other driver going via a dt tree.
Cheers,
Mark.
--
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