From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Shevchenko Date: Tue, 20 Nov 2018 20:27:28 +0200 Subject: [U-Boot] [PATCH v2 1/5] serial: Introduce ->getinfo() callback In-Reply-To: References: <20181115175854.7550-1-andriy.shevchenko@linux.intel.com> <20181115175854.7550-2-andriy.shevchenko@linux.intel.com> <48c60ce7-332a-d326-ca56-cc426a62d191@suse.de> Message-ID: <20181120182728.GD10650@smile.fi.intel.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Thu, Nov 15, 2018 at 09:09:55PM +0100, Alexander Graf wrote: > > > On 15.11.18 20:31, Andy Shevchenko wrote: > > On Thu, Nov 15, 2018 at 8:22 PM Alexander Graf wrote: > >> On 15.11.18 18:58, Andy Shevchenko wrote: > >>> New callback will give a necessary information to fill up ACPI SPCR table, > >>> for example. Maybe used later for other purposes. > > > >>> +/* REVISIT: ACPI GAS specification implied */ > >> > >> What does this REVISIT tag mean? > > > > Had you chance to read my cover letter? > > There is a section called "Known issues", item 3 there might answer to > > your question. > > The usual tag for "not finalized, please don't apply yet" in upstream > patch submissions is "RFC". If you don't think your code is ready to be > applied, just tag the patches with RFC, like this: > > [RFC] serial: Introduce ->getinfo() callback > > Then everyone knows that you don't think the patch is good enough yet. > Otherwise, every submission really implies that you think it should get > applied. > > As for the data structure itself, I think I gave you a bit of feedback. > I wouldn't worry too much about getting everything right from the start, > as this is a monolithic open source project. So changing the structure > later on is easy. Thanks, noted. -- With Best Regards, Andy Shevchenko