Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752626AbaKCOlJ (ORCPT ); Mon, 3 Nov 2014 09:41:09 -0500 Received: from mail-la0-f43.google.com ([209.85.215.43]:46248 "EHLO mail-la0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751972AbaKCOlF (ORCPT ); Mon, 3 Nov 2014 09:41:05 -0500 MIME-Version: 1.0 In-Reply-To: References: From: Rob Herring Date: Mon, 3 Nov 2014 08:40:41 -0600 Message-ID: Subject: Re: [PATCH 1/1] devicetree: bindings: Add vendor prefix for Micron Technology Co., Ltd. To: bpqw Cc: Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Jason Cooper , Mark Brown , Heiko Stuebner , Thierry Reding , Florian Vaussard , Andrew Lunn , Silvio F , Hayato Suzuki , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 3, 2014 at 8:28 AM, bpqw wrote: >>This patch is used to add vendor prefix for >>Micron Technology Inc in the vendor-prefixes.txt file. > >>Micron Technology, Inc. is an American >>multinational corporation based in Boise, >>Idaho, best known for producing many forms >>of semiconductor devices. This includes DRAM, >>SDRAM, flash memory, eMMC and SSDs. > >>Signed-off-by: bean huo > > Dear linux developer: > > Is there maintainer in this mail list? Can give me a result for > this simple patch?if can be accepted or not? Or give me some suggections? > It has been long time. It has been 6 minutes since you sent the last version. I see you have fixed the line length although I'm not sure why you made it so short. 72 characters is the norm, but up to 80 is fine. You have not fixed the authorship as Mark pointed out. Also, please version your patches (i.e. [PATCH v2]). Rob -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/