($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: patchwork-bot+ofono@kernel.org
To: Denis Kenzior <denkenz@gmail.com>
Cc: ofono@lists.linux.dev
Subject: Re: [PATCH 1/2] treewide: Make modem drivers builtin
Date: Tue, 20 Feb 2024 15:30:28 +0000	[thread overview]
Message-ID: <170844302821.30347.16187929099827928902.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240215193625.1140095-1-denkenz@gmail.com>

Hello:

This series was applied to ofono.git (master)
by Denis Kenzior <denkenz@gmail.com>:

On Thu, 15 Feb 2024 13:36:22 -0600 you wrote:
> Modem drivers are currently defined as plugins that register a
> modem driver via ofono_modem_driver_register in the plugin init
> method.  While oFono supports external plugins, this functionality
> hasn't been used in practice for a long time.  External modem drivers is
> also something that upstream project no longer wants to support.
> 
> Make all modem drivers builtin and introduce a new macro to make this
> explicit.  Remove ofono_modem_driver_register and
> ofono_modem_driver_unregister methods.
> 
> [...]

Here is the summary with links:
  - [1/2] treewide: Make modem drivers builtin
    (no matching commit)
  - [2/2] caif: Remove caif plugin
    https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=772eac040735

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-02-20 15:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15 19:36 [PATCH 1/2] treewide: Make modem drivers builtin Denis Kenzior
2024-02-15 19:36 ` [PATCH 2/2] caif: Remove caif plugin Denis Kenzior
2024-02-15 21:53 ` [PATCH 1/2] treewide: Make modem drivers builtin piggz1
2024-02-16 13:08   ` Marcel Holtmann
2024-02-20 15:30 ` patchwork-bot+ofono [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=170844302821.30347.16187929099827928902.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+ofono@kernel.org \
    --cc=denkenz@gmail.com \
    --cc=ofono@lists.linux.dev \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).