All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
To: Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	Artem Bityutskiy
	<artem.bityutskiy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] mtd/m25p80: add device tree probe support
Date: Mon, 25 Jun 2012 18:01:22 +0200	[thread overview]
Message-ID: <201206251801.22385.marex@denx.de> (raw)
In-Reply-To: <20120625154006.GB2342-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>

Dear Shawn Guo,

> On Sat, Jun 23, 2012 at 04:15:18AM +0200, Marek Vasut wrote:
> > So is there any particular reason why this wasn't applied?
> 
> Let me remind Artem by resending the patch tomorrow.

Actually ... the SPI does have the heuristics to probe this chip without the 
patch. But there was this discussion about them eventually being removed. That 
was a point raised by you I think. Is that still valid?

Best regards,
Marek Vasut

WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marex@denx.de>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: manu <manuel.pezzin@free.fr>,
	patches@linaro.org, devicetree-discuss@lists.ozlabs.org,
	Grant Likely <grant.likely@secretlab.ca>,
	linux-mtd@lists.infradead.org,
	Artem Bityutskiy <artem.bityutskiy@intel.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mtd/m25p80: add device tree probe support
Date: Mon, 25 Jun 2012 18:01:22 +0200	[thread overview]
Message-ID: <201206251801.22385.marex@denx.de> (raw)
In-Reply-To: <20120625154006.GB2342@S2101-09.ap.freescale.net>

Dear Shawn Guo,

> On Sat, Jun 23, 2012 at 04:15:18AM +0200, Marek Vasut wrote:
> > So is there any particular reason why this wasn't applied?
> 
> Let me remind Artem by resending the patch tomorrow.

Actually ... the SPI does have the heuristics to probe this chip without the 
patch. But there was this discussion about them eventually being removed. That 
was a point raised by you I think. Is that still valid?

Best regards,
Marek Vasut

WARNING: multiple messages have this Message-ID (diff)
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mtd/m25p80: add device tree probe support
Date: Mon, 25 Jun 2012 18:01:22 +0200	[thread overview]
Message-ID: <201206251801.22385.marex@denx.de> (raw)
In-Reply-To: <20120625154006.GB2342@S2101-09.ap.freescale.net>

Dear Shawn Guo,

> On Sat, Jun 23, 2012 at 04:15:18AM +0200, Marek Vasut wrote:
> > So is there any particular reason why this wasn't applied?
> 
> Let me remind Artem by resending the patch tomorrow.

Actually ... the SPI does have the heuristics to probe this chip without the 
patch. But there was this discussion about them eventually being removed. That 
was a point raised by you I think. Is that still valid?

Best regards,
Marek Vasut

  parent reply	other threads:[~2012-06-25 16:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25 13:37 [PATCH] mtd/m25p80: add device tree probe support Shawn Guo
2011-07-25 13:37 ` Shawn Guo
2011-07-25 13:37 ` Shawn Guo
     [not found] ` <1311601063-16581-1-git-send-email-shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2011-07-25 21:19   ` Grant Likely
2011-07-25 21:19     ` Grant Likely
2011-07-25 21:19     ` Grant Likely
2011-07-28 19:22     ` manu
2011-07-28 19:22       ` manu
2011-07-28 19:22       ` manu
     [not found]       ` <4E31B713.1030901-GANU6spQydw@public.gmane.org>
2011-07-28 21:45         ` Grant Likely
2011-07-28 21:45           ` Grant Likely
2011-07-28 21:45           ` Grant Likely
     [not found]           ` <20110728214521.GA4674-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2012-06-23  2:15             ` Marek Vasut
2012-06-23  2:15               ` Marek Vasut
2012-06-23  2:15               ` Marek Vasut
     [not found]               ` <201206230415.18833.marex-ynQEQJNshbs@public.gmane.org>
2012-06-25 15:40                 ` Shawn Guo
2012-06-25 15:40                   ` Shawn Guo
2012-06-25 15:40                   ` Shawn Guo
     [not found]                   ` <20120625154006.GB2342-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2012-06-25 16:01                     ` Marek Vasut [this message]
2012-06-25 16:01                       ` Marek Vasut
2012-06-25 16:01                       ` Marek Vasut
2012-06-25 16:15                       ` Shawn Guo
2012-06-25 16:15                         ` Shawn Guo
     [not found]                         ` <20120625161506.GH2342-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2012-06-25 16:50                           ` Marek Vasut
2012-06-25 16:50                             ` Marek Vasut
2012-06-25 16:50                             ` Marek Vasut
     [not found]                             ` <201206251850.10839.marex-ynQEQJNshbs@public.gmane.org>
2012-06-26  8:15                               ` Shawn Guo
2012-06-26  8:15                                 ` Shawn Guo
2012-06-26  8:15                                 ` Shawn Guo
     [not found]                                 ` <20120626081546.GB4928-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2012-06-26 11:47                                   ` Marek Vasut
2012-06-26 11:47                                     ` Marek Vasut
2012-06-26 11:47                                     ` Marek Vasut

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=201206251801.22385.marex@denx.de \
    --to=marex-ynqeqjnshbs@public.gmane.org \
    --cc=artem.bityutskiy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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.