From: Oskar Senft <osk@google.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 1/2] misc: aspeed: Add Aspeed UART routing control driver.
Date: Wed, 5 Sep 2018 09:45:38 -0400 [thread overview]
Message-ID: <CABoTLcQpyaLUtdSPJQ4v5_Ds2o54sDJxk+9_etthwQwWRoYK-Q@mail.gmail.com> (raw)
In-Reply-To: <CABoTLcRpQhC7L+Yk2uR91TJSB21i0cp+3BH5cgZWYOWmN6PzVQ@mail.gmail.com>
I just had a look at the upstream kernel - there's no drivers/soc/aspeed. I
did find drivers/soc, but no subdirectory for aspeed. Should I create that
with my commit?
Oskar.
On Tue, Sep 4, 2018 at 8:19 PM Oskar Senft <osk@google.com> wrote:
> Thanks for the input!
>
> I had a look at get_maintainer.pl, but thought I'd send it to you and
> Linus first to get initial input since we had already talked about it.
>
> I'll move it to drivers/soc/aspeed and will resend.
>
> For clarification: Should I send to ALL of the people and lists that
> get_maintainer.pl spits out?
>
> Thanks
> Oskar.
>
> On Tue, Sep 4, 2018 at 8:15 PM Andrew Jeffery <andrew@aj.id.au> wrote:
>
>> On Wed, 5 Sep 2018, at 07:25, Linus Walleij wrote:
>> > On Tue, Sep 4, 2018 at 10:20 PM Oskar Senft <osk@google.com> wrote:
>> >
>> > > This driver adds sysfs files that allow the BMC userspace to configure
>> > > how UARTs and physical serial I/O ports are routed.
>> > >
>> > > Tested: Checked correct behavior (both read & write) on TYAN S7106
>> > > board by manually changing routing settings and confirming that bits
>> > > flow as expected. Tested for UART1 and UART3 as this board doesn't
>> have
>> > > the other UARTs wired up in a testable way.
>> > >
>> > > Signed-off-by: Oskar Senft <osk@google.com>
>> >
>> > After reading some other messages about this I realize it's not very
>> > much you can do with the standard frameworks and you definately
>> > need something like this. Not like I have any better idea.
>> >
>> > Arnd and Greg are misc maintainers so not you will need to
>> > talk to them.
>>
>> Yes. I'm certainly not a person that can merge them.
>>
>> Oskar: Please add at least Greg and Arnd as Linus suggests, and in the
>> future make use of ./scripts/get_maintainer.pl to identify people and
>> lists who should receive the patches.
>>
>> >
>> > I would opt to put it in drivers/soc/aspeed though.
>>
>> Yep, drivers/soc/aspeed seems like a better place. There are other
>> drivers in misc likely should be moved there as well.
>>
>> Thanks for your feedback Linus.
>>
>> Andrew
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/linux-aspeed/attachments/20180905/4c4250e1/attachment-0001.html>
next prev parent reply other threads:[~2018-09-05 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 20:20 Aspeed UART routing driver Oskar Senft
2018-09-04 20:20 ` [PATCH 1/2] misc: aspeed: Add Aspeed UART routing control driver Oskar Senft
2018-09-04 21:55 ` Linus Walleij
2018-09-05 0:15 ` Andrew Jeffery
2018-09-05 0:19 ` Oskar Senft
2018-09-05 6:06 ` Linus Walleij
2018-09-05 13:45 ` Oskar Senft [this message]
2018-09-05 19:27 ` Linus Walleij
2018-09-04 20:20 ` [PATCH 2/2] arch: arm: boot: dts: aspeed: Add UART routing driver to Aspeed G5 DTS Oskar Senft
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=CABoTLcQpyaLUtdSPJQ4v5_Ds2o54sDJxk+9_etthwQwWRoYK-Q@mail.gmail.com \
--to=osk@google.com \
--cc=linux-aspeed@lists.ozlabs.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).