All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Chuanhong Guo <gch981213@gmail.com>
Cc: Armando Miraglia <arma2ff0@gmail.com>,
	NeilBrown <neil@brown.name>, Armando Miraglia <armax@google.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Stefan Roese <sr@denx.de>,
	sankalpnegi2310@gmail.com, devel@driverdev.osuosl.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: mediatek: Attempt to address style issues in spi-mt7621.c
Date: Wed, 13 Mar 2019 17:46:22 +0100	[thread overview]
Message-ID: <4789d739-d2b5-357b-b9d8-bfaf587d33fc@gmail.com> (raw)
In-Reply-To: <CAJsYDVKF-3jZo4E3EMiYOqeWXVLu0hBra6Qp0sFoCz8y=BAjSw@mail.gmail.com>



On 13/03/2019 17:34, Chuanhong Guo wrote:
> Hi!
> On Wed, Mar 13, 2019 at 8:28 PM Matthias Brugger <matthias.bgg@gmail.com> wrote:
>>
>>
>>
>> On 13/03/2019 13:24, Armando Miraglia wrote:
>> [...]
>> Apart from fixing styling issues it would be usefull to see if we can add
>> support for mt7621 to drivers/spi/spi-mt65xx.c
> It's impossible. They are completely different IPs.

Thanks for the info. Do you know the status of the rest of the drivers in staging?

Best regards,
Matthias

WARNING: multiple messages have this Message-ID (diff)
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Chuanhong Guo <gch981213@gmail.com>
Cc: devel@driverdev.osuosl.org, sankalpnegi2310@gmail.com,
	linux-kernel@vger.kernel.org, NeilBrown <neil@brown.name>,
	Armando Miraglia <armax@google.com>,
	linux-mediatek@lists.infradead.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Armando Miraglia <arma2ff0@gmail.com>, Stefan Roese <sr@denx.de>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] spi: mediatek: Attempt to address style issues in spi-mt7621.c
Date: Wed, 13 Mar 2019 17:46:22 +0100	[thread overview]
Message-ID: <4789d739-d2b5-357b-b9d8-bfaf587d33fc@gmail.com> (raw)
In-Reply-To: <CAJsYDVKF-3jZo4E3EMiYOqeWXVLu0hBra6Qp0sFoCz8y=BAjSw@mail.gmail.com>



On 13/03/2019 17:34, Chuanhong Guo wrote:
> Hi!
> On Wed, Mar 13, 2019 at 8:28 PM Matthias Brugger <matthias.bgg@gmail.com> wrote:
>>
>>
>>
>> On 13/03/2019 13:24, Armando Miraglia wrote:
>> [...]
>> Apart from fixing styling issues it would be usefull to see if we can add
>> support for mt7621 to drivers/spi/spi-mt65xx.c
> It's impossible. They are completely different IPs.

Thanks for the info. Do you know the status of the rest of the drivers in staging?

Best regards,
Matthias

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-03-13 16:46 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 12:24 [PATCH] spi: mediatek: Attempt to address style issues in spi-mt7621.c Armando Miraglia
2019-03-13 12:24 ` Armando Miraglia
2019-03-13 12:28 ` Matthias Brugger
2019-03-13 12:28   ` Matthias Brugger
2019-03-13 12:28   ` Matthias Brugger
2019-03-13 12:31   ` Armando Miraglia
2019-03-13 12:31     ` Armando Miraglia
2019-03-13 16:34   ` Chuanhong Guo
2019-03-13 16:34     ` Chuanhong Guo
2019-03-13 16:46     ` Matthias Brugger [this message]
2019-03-13 16:46       ` Matthias Brugger
2019-03-13 16:54       ` Stefan Roese
2019-03-13 16:54         ` Stefan Roese
2019-03-13 22:14         ` NeilBrown
2019-03-13 22:14           ` NeilBrown
2019-03-14  2:26           ` Chuanhong Guo
2019-03-14  2:26             ` Chuanhong Guo
2019-03-14  2:26             ` Chuanhong Guo
2019-03-14  2:36             ` NeilBrown
2019-03-14  2:36               ` NeilBrown
2019-03-13 12:34 ` Dan Carpenter
2019-03-13 12:34   ` Dan Carpenter
2019-03-13 12:34   ` Dan Carpenter
2019-03-13 16:47   ` Matthias Brugger
2019-03-13 16:47     ` Matthias Brugger
2019-03-14 11:13   ` Armando Miraglia
2019-03-14 11:13     ` Armando Miraglia
2019-03-14 11:27     ` Dan Carpenter
2019-03-14 11:27       ` Dan Carpenter
2019-03-14 11:27       ` Dan Carpenter
2019-03-14 14:07       ` Jean Delvare
2019-03-14 14:07         ` Jean Delvare
2019-03-14 20:50         ` Joe Perches
2019-03-14 20:50           ` Joe Perches
2019-03-14 11:36     ` Stefan Roese
2019-03-14 11:36       ` Stefan Roese
2019-03-14 11:37       ` Armando Miraglia
2019-03-14 11:37         ` Armando Miraglia
2019-03-14 13:14         ` Matthias Brugger
2019-03-14 13:14           ` Matthias Brugger
2019-03-14 13:14           ` Matthias Brugger
2019-03-14 13:24           ` Stefan Roese
2019-03-14 13:24             ` Stefan Roese
2019-03-14 17:01             ` Matthias Brugger
2019-03-14 17:01               ` Matthias Brugger
  -- strict thread matches above, loose matches on Subject: below --
2019-03-13 11:57 Armando Miraglia

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=4789d739-d2b5-357b-b9d8-bfaf587d33fc@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=arma2ff0@gmail.com \
    --cc=armax@google.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gch981213@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=neil@brown.name \
    --cc=sankalpnegi2310@gmail.com \
    --cc=sr@denx.de \
    /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.