linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chen-Yu Tsai <wens@csie.org>
To: Mark Brown <broonie@kernel.org>
Cc: dinghua ma <dinghua.ma.sz@gmail.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	stable <stable@vger.kernel.org>
Subject: Re: [PATCH v2] regulatx DLDO2 voltage control register mask for AXP22x
Date: Sat, 5 Dec 2020 01:56:38 +0800	[thread overview]
Message-ID: <CAGb2v65mRo7sTZZ65P75vs9os198kUh-OyhewdDCkjyUhXuV6Q@mail.gmail.com> (raw)
In-Reply-To: <20201204174020.GB4558@sirena.org.uk>

On Sat, Dec 5, 2020 at 1:40 AM Mark Brown <broonie@kernel.org> wrote:
>
> On Fri, Dec 04, 2020 at 10:34:21AM +0800, Chen-Yu Tsai wrote:
> > On Thu, Dec 3, 2020 at 12:11 AM Mark Brown <broonie@kernel.org> wrote:
>
> > > No, no sign.  You can check if things are at least hitting the list at:
>
> > >     https://lore.kernel.org/lkml/
>
> > I did receive it though. Would it help if I tried to bounce it to you
> > and the lists?
>
> Possibly?  It depends on what the issue is.

Looks like v3 was already there the first time though:

https://lore.kernel.org/lkml/20201201001000.22302-1-dinghua.ma.sz@gmail.com/

Me bouncing it again had no real effect.


ChenYu

  reply	other threads:[~2020-12-04 17:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201130234520.13255-1-dinghua.ma.sz@gmail.com>
     [not found] ` <CA+Jj2f8ADtb8JPPPzafvgVM0jssk8fz_BS-3LDUaYjZHcouTJQ@mail.gmail.com>
2020-12-01 15:00   ` [PATCH v2] regulatx DLDO2 voltage control register mask for AXP22x Mark Brown
     [not found]     ` <CA+Jj2f9=oCxdnaHJTtPXwvwokRX9HRMDYUNrbDASmV+FoTefvQ@mail.gmail.com>
2020-12-02 16:10       ` Mark Brown
2020-12-04  2:34         ` Chen-Yu Tsai
2020-12-04 17:40           ` Mark Brown
2020-12-04 17:56             ` Chen-Yu Tsai [this message]
2020-12-04 20:34               ` Mark Brown

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=CAGb2v65mRo7sTZZ65P75vs9os198kUh-OyhewdDCkjyUhXuV6Q@mail.gmail.com \
    --to=wens@csie.org \
    --cc=broonie@kernel.org \
    --cc=dinghua.ma.sz@gmail.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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).