linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: matthias.bgg@gmail.com (Matthias Brugger)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Mediatek: soc driver updates for v4.15
Date: Thu, 2 Nov 2017 19:40:43 +0100	[thread overview]
Message-ID: <514a12ee-b31f-1be0-8e11-2ec0929dd34b@gmail.com> (raw)
In-Reply-To: <CAK8P3a1hCWV6Fp5wyiESbdZUsgSoGZywj55=0v9Az-TPt3GtyQ@mail.gmail.com>

Hi Arnd,

On 11/02/2017 04:35 PM, Arnd Bergmann wrote:
> On Mon, Oct 23, 2017 at 12:10 AM, Matthias Brugger
> <matthias.bgg@gmail.com> wrote:
>>
>> ----------------------------------------------------------------
>> - add 32 bit read/write support to pwrap
>> - add mt7622 support to pwrap
>> - test build all mediatek soc drivers
>> - fix compiler issues
>> - clean up Kconfig description
> 
> Pulled into next/soc. I see some bug fixes in here that I would have
> marked 'Cc: stable at vger.kernel.org'
> to get them backported into stable kernels. Could you please make sure
> they are marked appropriately
> in the future, and maybe (after the merge window) send a message to
> stable at vger.kernel.org with a list
> of the commits that you want backported but that are missing the tag? Thanks!
> 

Do you refer to this commits?
f32fbbadaf44 soc: mediatek: pwrap: fix fatal compiler error
fb2c1934f305 soc: mediatek: pwrap: fix compiler errors

They are actually fix problems in the very same pull request.

Regards,
Matthias

  reply	other threads:[~2017-11-02 18:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1ebc2f2d-033e-e8d6-86c8-32a67ebd55b7@gmail.com>
2017-10-22 22:12 ` [GIT PULL] Mediatek: soc driver updates for v4.15 Matthias Brugger
2017-11-02 15:35 ` Arnd Bergmann
2017-11-02 18:40   ` Matthias Brugger [this message]
2017-11-02 21:51     ` Arnd Bergmann

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=514a12ee-b31f-1be0-8e11-2ec0929dd34b@gmail.com \
    --to=matthias.bgg@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).