linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Serge Semin <fancer.lancer@gmail.com>,
	Ding Tianhong <dingtianhong@huawei.com>,
	Hoan Tran <hoan@os.amperecomputing.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	kernel.openeuler@huawei.com
Subject: Re: [PATCH] gpio: dwapb: add support for new hisilicon ascend soc
Date: Fri, 28 Aug 2020 20:21:40 +0200	[thread overview]
Message-ID: <CAMpxmJUEvaW82V8s8Tw2MVGVb4Tgkg6T9-NfFJye7zF+j2a-ig@mail.gmail.com> (raw)
In-Reply-To: <CAHp75VfnCRFPQ19tdQb46PvnBV3RActKn4+hSivPN8e122Q1Aw@mail.gmail.com>

On Thu, Aug 27, 2020 at 10:20 AM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
>
> On Tue, Aug 25, 2020 at 12:58 PM Serge Semin <fancer.lancer@gmail.com> wrote:
> > On Sat, Aug 22, 2020 at 12:27:53PM +0800, Ding Tianhong wrote:
>
> > BTW Linus, could you take a look at my series? Andy and Rob have finished reviewing
> > it almost a month ago.
>
> I was wondering the same, but in normal cases (not closer to the merge
> window) Bart is taking care of drivers/gpio (AFAIU).
>
>

Yeah, normally I'd have queued it by now but I'm only coming back to
100% activity on Tuesday - I was on a leave since July so I was rather
inactive lately.

Bartosz

  parent reply	other threads:[~2020-08-28 18:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-22  4:27 [PATCH] gpio: dwapb: add support for new hisilicon ascend soc Ding Tianhong
2020-08-25  9:57 ` Serge Semin
2020-08-27  8:19   ` Andy Shevchenko
2020-08-27  8:34     ` Linus Walleij
2020-08-28 18:21     ` Bartosz Golaszewski [this message]
     [not found]   ` <856a6200-2bbb-9ffa-9233-53168bd7c49b@huawei.com>
2020-09-12 13:31     ` Serge Semin

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=CAMpxmJUEvaW82V8s8Tw2MVGVb4Tgkg6T9-NfFJye7zF+j2a-ig@mail.gmail.com \
    --to=bgolaszewski@baylibre.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=dingtianhong@huawei.com \
    --cc=fancer.lancer@gmail.com \
    --cc=hoan@os.amperecomputing.com \
    --cc=kernel.openeuler@huawei.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).