mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Sam Protsenko <semen.protsenko@linaro.org>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	linux-watchdog@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] watchdog: s3c2410: Fix getting the optional clock
Date: Tue, 21 Dec 2021 07:05:09 -0800	[thread overview]
Message-ID: <20211221150509.GA2753412@roeck-us.net> (raw)
In-Reply-To: <CAPLW+4=ZoBqhLpNPiknTjqMXK5wJtOJtn4=99_kvaC3DBb_eqQ@mail.gmail.com>

On Tue, Dec 21, 2021 at 01:52:32PM +0200, Sam Protsenko wrote:
> On Mon, 20 Dec 2021 at 23:08, Guenter Roeck <linux@roeck-us.net> wrote:
[ ... ]
> >
> > I added the patch to my watchdog-next tree, but Wim handles all pull
> > requests.
> >
> 
> Thanks, Guenter! Do I need to take any other actions, or Wim is going
> to take patches from your tree? I just checked [1] (master branch),
> and I can't see my patches there yet.
> 
> [1] git://www.linux-watchdog.org/linux-watchdog-next.git
> 
Wim usually takes patches either from my tree or from the list,
but he does so shortly before the commit window opens. You don't
need to do anything else.

Guenter

      reply	other threads:[~2021-12-21 15:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-12 17:02 Sam Protsenko
2021-12-12 17:37 ` Guenter Roeck
2021-12-12 17:50 ` Krzysztof Kozlowski
2021-12-20 15:15   ` Sam Protsenko
2021-12-20 21:08     ` Guenter Roeck
2021-12-21 11:52       ` Sam Protsenko
2021-12-21 15:05         ` Guenter Roeck [this message]

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=20211221150509.GA2753412@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=dan.carpenter@oracle.com \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=semen.protsenko@linaro.org \
    --cc=wim@linux-watchdog.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

all inboxes | Powered by JetHome®