All of lore.kernel.org
 help / color / mirror / Atom feed
From: dinguyen@opensource.altera.com (Dinh Nguyen)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] SOCFPGA updates for 3.18
Date: Tue, 9 Sep 2014 11:04:12 -0500	[thread overview]
Message-ID: <540F24FC.2070008@opensource.altera.com> (raw)
In-Reply-To: <15438682.g2WSItt3Xr@wuerfel>

On 09/09/2014 09:55 AM, Arnd Bergmann wrote:
> On Thursday 04 September 2014 11:11:44 dinguyen at opensource.altera.com wrote:
>> Hi Arnd, Kevin and Olof,
>>
>> Please consider pulling in these patches for v3.18. 5 of the 6 patches are
>> DTS updates and the 1 patch is updating the MAINTAINERS entry with my new
>> email address.
> 
> Pulled into next/dt. It would be nice if you could in the future
> separate the DT updates from the other changes more, even if that means
> sending a separate patch or pull request for something as trivial as
> the MAINTAINERS update.

Will keep this in mind in the future.
> 
> For some reason your pull request ended up in my spam folder, where
> I only found it today when looking for something else. I don't know
> why this happened, but you might want to watch out for this happening
> again, and ping us if a future pull request doesn't get merged within
> a couple of days. 
> 

I was going to give it a week.

>>
>> The following changes since commit 52addcf9d6669fa439387610bc65c92fa0980cef:
>>
>>   Linux 3.17-rc2 (2014-08-25 15:36:20 -0700)
>>
>> are available in the git repository at:
>>
>>   git://git.rocketboards.org/linux-socfpga-next.git tags/socfpga_update_for_v3.18
>>
>> for you to fetch changes up to 75a41826e2c5dc1dc0fd5195fc29b031c97337af:
>>
>>   arm: dts: Add Altera SDRAM EDAC bindings & devicetree entries. (2014-09-04 10:15:52 -0500)
>>
>> ----------------------------------------------------------------
>> arm: dts: Add Altera SDRAM EDAC bindings & devicetree entries.
>>
> 
> Please try to be a little more verbose with the changelog, as this
> is what ends up in the git history for the merge commit.
> 

Will do...

Thanks,
Dinh

      reply	other threads:[~2014-09-09 16:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 16:11 [GIT PULL 1/2] SOCFPGA updates for 3.18 dinguyen at opensource.altera.com
2014-09-04 16:11 ` [GIT PULL 2/2] SOCFPGA driver " dinguyen at opensource.altera.com
2014-09-09 14:59   ` Arnd Bergmann
2014-09-09 15:45     ` Borislav Petkov
2014-09-09 15:53       ` Arnd Bergmann
2014-09-09 18:40         ` Borislav Petkov
2014-09-09 14:17 ` [GIT PULL 1/2] SOCFPGA " Pavel Machek
2014-09-09 15:02   ` Arnd Bergmann
2014-09-09 15:02     ` Arnd Bergmann
2014-09-09 21:02     ` Pavel Machek
2014-09-09 21:02       ` Pavel Machek
2014-09-10  7:13       ` Ulf Hansson
2014-09-10  7:13         ` Ulf Hansson
2014-09-10  8:33         ` Pavel Machek
2014-09-10  8:33           ` Pavel Machek
2014-09-10 10:42           ` Ulf Hansson
2014-09-10 10:42             ` Ulf Hansson
2014-09-10 11:00             ` Pavel Machek
2014-09-10 11:00               ` Pavel Machek
2014-09-10 14:19               ` Dinh Nguyen
2014-09-10 14:19                 ` Dinh Nguyen
2014-09-10 14:36       ` Marek Vasut
2014-09-10 14:36         ` Marek Vasut
2014-09-09 14:55 ` Arnd Bergmann
2014-09-09 16:04   ` Dinh Nguyen [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=540F24FC.2070008@opensource.altera.com \
    --to=dinguyen@opensource.altera.com \
    --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.