All of lore.kernel.org
 help / color / mirror / Atom feed
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] arm: mxs: Various mxs_defconfig adjustments
Date: Fri, 21 Dec 2012 03:03:20 +0100	[thread overview]
Message-ID: <201212210303.20834.marex@denx.de> (raw)
In-Reply-To: <CAAQ0ZWSxdfWzaHfr2eVazRHp-eGBdHFyVb-P_ib_6xmoGWXQdw@mail.gmail.com>

Dear Shawn Guo,

> On Thu, Dec 20, 2012 at 01:44:27PM +0100, Marek Vasut wrote:
> > Dear Shawn Guo,
> > 
> > > On Wed, Dec 19, 2012 at 06:32:58PM +0100, Marek Vasut wrote:
> > > > This patchset enables various config options, mostly needed to
> > > > get MX28EVK and M28EVK decently working.
> > > > 
> > > > Marek Vasut (8):
> > > >   arm: mxs: Regenerate mxs_defconfig to match recent kernel
> > > >   arm: mxs: Enable MTD block access
> > > >   arm: mxs: Enable UBI and UBIFS
> > > >   arm: mxs: Enable JFFS2
> > > >   arm: mxs: Enable EXT2 and EXT4
> > > >   arm: mxs: Enable AT24 EEPROM support
> > > >   arm: mxs: Enable support for most SPI flashes
> > > >   arm: mxs: Enable most commonly used PHYs
> > > 
> > > It does not need to be so verbose.  It can just be one patch.
> > 
> > Do you prefer one gigantic patch then?
> 
> I do not take "1 file changed, 30 insertions(+), 33 deletions(-)" as
> a gigantic change set, especially when it's on defconfig.  Just remember
> to run savedefconfig before you submit the changes.

Sure, one big nasty patch on it's way to your mailbox then.

I wanted to keep the changes separate to make them obvious and clear, that was 
my whole motivation, nothing else.

[...]

Best regards,
Marek Vasut

      reply	other threads:[~2012-12-21  2:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19 17:32 [PATCH 0/8] arm: mxs: Various mxs_defconfig adjustments Marek Vasut
2012-12-19 17:32 ` [PATCH 1/8] arm: mxs: Regenerate mxs_defconfig to match recent kernel Marek Vasut
2012-12-19 17:33 ` [PATCH 2/8] arm: mxs: Enable MTD block access Marek Vasut
2012-12-19 17:33 ` [PATCH 3/8] arm: mxs: Enable UBI and UBIFS Marek Vasut
2012-12-19 17:33 ` [PATCH 4/8] arm: mxs: Enable JFFS2 Marek Vasut
2012-12-19 17:33 ` [PATCH 5/8] arm: mxs: Enable EXT2 and EXT4 Marek Vasut
2012-12-19 17:33 ` [PATCH 6/8] arm: mxs: Enable AT24 EEPROM support Marek Vasut
2012-12-19 17:33 ` [PATCH 7/8] arm: mxs: Enable support for most SPI flashes Marek Vasut
2012-12-19 17:33 ` [PATCH 8/8] arm: mxs: Enable most commonly used PHYs Marek Vasut
2012-12-20  5:51 ` [PATCH 0/8] arm: mxs: Various mxs_defconfig adjustments Shawn Guo
2012-12-20 12:44   ` Marek Vasut
2012-12-21  1:58     ` Shawn Guo
2012-12-21  2:03       ` Marek Vasut [this message]

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=201212210303.20834.marex@denx.de \
    --to=marex@denx.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.