All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Girish KS <girishks2000@gmail.com>
Cc: Mark Brown <broonie@kernel.org>,
	spi-devel-general@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, grant.likely@secretlab.ca,
	t.figa@samsung.com
Subject: Re: [PATCH V4 2/5] spi: s3c64xx: added support for polling mode
Date: Tue, 16 Apr 2013 13:12:55 +0100	[thread overview]
Message-ID: <20130416121255.GA15878@sirena.org.uk> (raw)
In-Reply-To: <CAKrE-Kd4Vis0-V_n8zEzqJVBbEYvTiYS8hY_7s7AnUqaK2tFCQ@mail.gmail.com>

On Tue, Apr 16, 2013 at 04:58:47PM +0530, Girish KS wrote:
> On Tue, Apr 16, 2013 at 4:50 PM, Mark Brown <broonie@kernel.org> wrote:

> > I'm missing patch 1 of this series.

> its already  merged to stable tree after your review

The patch numbering should reflect what you're posting.  If you're only
sending four patches they should be numbered 1-4, otherwise it looks
like there's something missing.  The goal with the numbers is to help
people get the patches in the right order, the name should be enough to
associate with other versions of the same patch.

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Girish KS <girishks2000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: t.figa-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH V4 2/5] spi: s3c64xx: added support for polling mode
Date: Tue, 16 Apr 2013 13:12:55 +0100	[thread overview]
Message-ID: <20130416121255.GA15878@sirena.org.uk> (raw)
In-Reply-To: <CAKrE-Kd4Vis0-V_n8zEzqJVBbEYvTiYS8hY_7s7AnUqaK2tFCQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Tue, Apr 16, 2013 at 04:58:47PM +0530, Girish KS wrote:
> On Tue, Apr 16, 2013 at 4:50 PM, Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:

> > I'm missing patch 1 of this series.

> its already  merged to stable tree after your review

The patch numbering should reflect what you're posting.  If you're only
sending four patches they should be numbered 1-4, otherwise it looks
like there's something missing.  The goal with the numbers is to help
people get the patches in the right order, the name should be enough to
associate with other versions of the same patch.

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter

WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 2/5] spi: s3c64xx: added support for polling mode
Date: Tue, 16 Apr 2013 13:12:55 +0100	[thread overview]
Message-ID: <20130416121255.GA15878@sirena.org.uk> (raw)
In-Reply-To: <CAKrE-Kd4Vis0-V_n8zEzqJVBbEYvTiYS8hY_7s7AnUqaK2tFCQ@mail.gmail.com>

On Tue, Apr 16, 2013 at 04:58:47PM +0530, Girish KS wrote:
> On Tue, Apr 16, 2013 at 4:50 PM, Mark Brown <broonie@kernel.org> wrote:

> > I'm missing patch 1 of this series.

> its already  merged to stable tree after your review

The patch numbering should reflect what you're posting.  If you're only
sending four patches they should be numbered 1-4, otherwise it looks
like there's something missing.  The goal with the numbers is to help
people get the patches in the right order, the name should be enough to
associate with other versions of the same patch.

  reply	other threads:[~2013-04-16 12:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15  8:40 [PATCH V4 2/5] spi: s3c64xx: added support for polling mode Girish K S
2013-04-15  8:40 ` Girish K S
2013-04-15  8:40 ` [PATCH V3 RESEND 3/5] spi: s3c64xx: Added provision for non-gpio i/o's Girish K S
2013-04-15  8:40   ` Girish K S
2013-04-15  8:40   ` Girish K S
2013-04-16 15:58   ` Mark Brown
2013-04-16 15:58     ` Mark Brown
2013-04-15  8:40 ` [PATCH V4 4/5] spi: s3c64xx: Added provision for dedicated cs pin Girish K S
2013-04-15  8:40   ` Girish K S
2013-04-15  8:40   ` Girish K S
2013-04-15  8:40 ` [PATCH RESEND V3 5/5] spi: s3c64xx: Added support for exynos5440 spi Girish K S
2013-04-15  8:40   ` Girish K S
2013-04-15  8:40   ` Girish K S
2013-04-16 11:20 ` [PATCH V4 2/5] spi: s3c64xx: added support for polling mode Mark Brown
2013-04-16 11:20   ` Mark Brown
2013-04-16 11:28   ` Girish KS
2013-04-16 11:28     ` Girish KS
2013-04-16 11:28     ` Girish KS
2013-04-16 12:12     ` Mark Brown [this message]
2013-04-16 12:12       ` Mark Brown
2013-04-16 12:12       ` Mark Brown
2013-04-17 10:22       ` Girish KS
2013-04-17 10:22         ` Girish KS
2013-04-17 10:22         ` Girish KS

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=20130416121255.GA15878@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=girishks2000@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spi-devel-general@lists.sourceforge.net \
    --cc=t.figa@samsung.com \
    /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.