All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cory Tusar <cory.tusar@pid1solutions.com>
To: Stefan Agner <stefan@agner.ch>, Holger Schurig <holgerschurig@gmail.com>
Cc: shawnguo@kernel.org, Sascha Hauer <kernel@pengutronix.de>,
	mark.rutland@arm.com, devicetree@vger.kernel.org,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	pawel.moll@arm.com, ijc+devicetree@hellion.org.uk,
	open list <linux-kernel@vger.kernel.org>,
	robh+dt@kernel.org, andrew@lunn.ch, galak@codeaurora.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/1] Add support for esdhc0 on Vybrid.
Date: Thu, 09 Jul 2015 08:40:01 -0400	[thread overview]
Message-ID: <559E6BA1.7030101@pid1solutions.com> (raw)
In-Reply-To: <63570c082077002155d3a99567664ef3@agner.ch>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/09/2015 02:13 AM, Stefan Agner wrote:
> On 2015-07-09 08:07, Holger Schurig wrote:
>>> Cory Tusar (1):
>>>   ARM: dts: vfxxx: Include support for esdhc0 functionality.
>>>
>>>  arch/arm/boot/dts/vfxxx.dtsi | 11 +++++++++++
>>>  1 file changed, 11 insertions(+)
>>>
>>> --
>>> 2.3.6
>>
>> Your patch looks empty.
> 
> This is a cover letter which provides overview over a whole patchset.
> The patch is a separate reply message of this mail (PATCH 1/1). 
> 
> @Cory
> However, it is unusual to use a cover letter when there is only a single
> patch. If you want to add additional comments which should not be part
> of the commit message, you can edit the patch and insert text after the
> three dashes, just before the diffstat. This text won't be part of the
> commit when applied later.

Hi Stefan,

Duly noted.  Appreciate the feedback, and will keep in mind for next
time.

Best regards,
- -Cory


- -- 
Cory Tusar
Principal
PID 1 Solutions, Inc.


"There are two ways of constructing a software design.  One way is to
 make it so simple that there are obviously no deficiencies, and the
 other way is to make it so complicated that there are no obvious
 deficiencies."  --Sir Charles Anthony Richard Hoare

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlWea6EACgkQHT1tsfGwHJ8CYACgqK20a6hhtl66aA+an5lWX4Ob
jTgAoKiygJTWpw9oYrmiZWk874tzkoZa
=YMvj
-----END PGP SIGNATURE-----

WARNING: multiple messages have this Message-ID (diff)
From: Cory Tusar <cory.tusar@pid1solutions.com>
To: Stefan Agner <stefan@agner.ch>, Holger Schurig <holgerschurig@gmail.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	pawel.moll@arm.com, ijc+devicetree@hellion.org.uk,
	open list <linux-kernel@vger.kernel.org>,
	robh+dt@kernel.org, andrew@lunn.ch,
	Sascha Hauer <kernel@pengutronix.de>,
	galak@codeaurora.org, shawnguo@kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/1] Add support for esdhc0 on Vybrid.
Date: Thu, 09 Jul 2015 08:40:01 -0400	[thread overview]
Message-ID: <559E6BA1.7030101@pid1solutions.com> (raw)
In-Reply-To: <63570c082077002155d3a99567664ef3@agner.ch>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/09/2015 02:13 AM, Stefan Agner wrote:
> On 2015-07-09 08:07, Holger Schurig wrote:
>>> Cory Tusar (1):
>>>   ARM: dts: vfxxx: Include support for esdhc0 functionality.
>>>
>>>  arch/arm/boot/dts/vfxxx.dtsi | 11 +++++++++++
>>>  1 file changed, 11 insertions(+)
>>>
>>> --
>>> 2.3.6
>>
>> Your patch looks empty.
> 
> This is a cover letter which provides overview over a whole patchset.
> The patch is a separate reply message of this mail (PATCH 1/1). 
> 
> @Cory
> However, it is unusual to use a cover letter when there is only a single
> patch. If you want to add additional comments which should not be part
> of the commit message, you can edit the patch and insert text after the
> three dashes, just before the diffstat. This text won't be part of the
> commit when applied later.

Hi Stefan,

Duly noted.  Appreciate the feedback, and will keep in mind for next
time.

Best regards,
- -Cory


- -- 
Cory Tusar
Principal
PID 1 Solutions, Inc.


"There are two ways of constructing a software design.  One way is to
 make it so simple that there are obviously no deficiencies, and the
 other way is to make it so complicated that there are no obvious
 deficiencies."  --Sir Charles Anthony Richard Hoare

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlWea6EACgkQHT1tsfGwHJ8CYACgqK20a6hhtl66aA+an5lWX4Ob
jTgAoKiygJTWpw9oYrmiZWk874tzkoZa
=YMvj
-----END PGP SIGNATURE-----

WARNING: multiple messages have this Message-ID (diff)
From: cory.tusar@pid1solutions.com (Cory Tusar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/1] Add support for esdhc0 on Vybrid.
Date: Thu, 09 Jul 2015 08:40:01 -0400	[thread overview]
Message-ID: <559E6BA1.7030101@pid1solutions.com> (raw)
In-Reply-To: <63570c082077002155d3a99567664ef3@agner.ch>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/09/2015 02:13 AM, Stefan Agner wrote:
> On 2015-07-09 08:07, Holger Schurig wrote:
>>> Cory Tusar (1):
>>>   ARM: dts: vfxxx: Include support for esdhc0 functionality.
>>>
>>>  arch/arm/boot/dts/vfxxx.dtsi | 11 +++++++++++
>>>  1 file changed, 11 insertions(+)
>>>
>>> --
>>> 2.3.6
>>
>> Your patch looks empty.
> 
> This is a cover letter which provides overview over a whole patchset.
> The patch is a separate reply message of this mail (PATCH 1/1). 
> 
> @Cory
> However, it is unusual to use a cover letter when there is only a single
> patch. If you want to add additional comments which should not be part
> of the commit message, you can edit the patch and insert text after the
> three dashes, just before the diffstat. This text won't be part of the
> commit when applied later.

Hi Stefan,

Duly noted.  Appreciate the feedback, and will keep in mind for next
time.

Best regards,
- -Cory


- -- 
Cory Tusar
Principal
PID 1 Solutions, Inc.


"There are two ways of constructing a software design.  One way is to
 make it so simple that there are obviously no deficiencies, and the
 other way is to make it so complicated that there are no obvious
 deficiencies."  --Sir Charles Anthony Richard Hoare

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlWea6EACgkQHT1tsfGwHJ8CYACgqK20a6hhtl66aA+an5lWX4Ob
jTgAoKiygJTWpw9oYrmiZWk874tzkoZa
=YMvj
-----END PGP SIGNATURE-----

  reply	other threads:[~2015-07-09 12:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 20:51 [PATCH 0/1] Add support for esdhc0 on Vybrid Cory Tusar
2015-07-08 20:51 ` Cory Tusar
2015-07-08 20:51 ` [PATCH 1/1] ARM: dts: vfxxx: Include support for esdhc0 functionality Cory Tusar
2015-07-08 20:51   ` Cory Tusar
2015-07-09 15:07   ` Stefan Agner
2015-07-09 15:07     ` Stefan Agner
2015-07-14  3:38   ` Shawn Guo
2015-07-14  3:38     ` Shawn Guo
2015-07-14  3:38     ` Shawn Guo
2015-07-09  6:07 ` [PATCH 0/1] Add support for esdhc0 on Vybrid Holger Schurig
2015-07-09  6:07   ` Holger Schurig
2015-07-09  6:07   ` Holger Schurig
2015-07-09  6:13   ` Stefan Agner
2015-07-09  6:13     ` Stefan Agner
2015-07-09 12:40     ` Cory Tusar [this message]
2015-07-09 12:40       ` Cory Tusar
2015-07-09 12:40       ` Cory Tusar

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=559E6BA1.7030101@pid1solutions.com \
    --to=cory.tusar@pid1solutions.com \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=holgerschurig@gmail.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=stefan@agner.ch \
    /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.