oe-linux-nfc.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: linux-nfc@lists.01.org
Subject: Re: [PATCH v2] ndef: Only register interface for known records
Date: Fri, 08 Nov 2019 10:05:01 +0100	[thread overview]
Message-ID: <20191108090501.GA278603@caravaggio> (raw)
In-Reply-To: <20191108040813.GA19844@animalcreek.com>

[-- Attachment #1: Type: text/plain, Size: 1537 bytes --]

Hi Mark, Ricardo,

On Thu, Nov 07, 2019 at 09:08:13PM -0700, Mark Greer wrote:
> On Wed, Nov 06, 2019 at 03:13:26PM +0100, Ricardo Ribalda Delgado wrote:
> > Hi
> > 
> > This is just my yearly ping to check if it has been merged ;)
> > 
> > Best regards
> > 
> > On Mon, Oct 1, 2018 at 1:35 AM Mark Greer <mgreer@animalcreek.com> wrote:
> > >
> > > On Tue, Sep 18, 2018 at 08:19:52AM +0200, Ricardo Ribalda Delgado wrote:
> > > > If we register the interface for unknown/error records neard daemon will
> > > > crash with no useful output message.
> > > > https://lists.01.org/pipermail/linux-nfc/2018-September/004445.html
> > > >
> > > > ...
> > > > neard[2404]: src/ndef.c:aar_exists() No AAR
> > > > neard[2404]: src/ndef.c:mime_payload_exists() No MIME payload
> > > > neard[2404]: D-Bus disconnect
> > > > neard[2404]: D-Bus disconnect (BT)
> > > > ...
> > > >
> > > > Signed-off-by: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
> > > > ---
> > >
> > > FWIW,
> > >
> > > Reviewed-by: Mark Greer <mgreer@animalcreek.com>
> 
> Hi Ricardo.
> 
> I don't think anyone is maintaining neard nowadays.  :(

I would say that's correct. I moved on to different areas and don't have
time to maintain it anymore. I also released my kernel NFC maintainer
role. Sorry about that.

> I don't really have any suggestions for you on how to proceed.
> 
> Samuel, any thoughts?

What about moving the neard repo to github and have you or Ricardo (or
both) maintain it from there?

Cheers,
Samuel.

       reply	other threads:[~2019-11-08  9:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191108040813.GA19844@animalcreek.com>
2019-11-08  9:05 ` Samuel Ortiz [this message]
     [not found] <20191109203830.GA31348@animalcreek.com>
2019-11-10 16:37 ` [PATCH v2] ndef: Only register interface for known records Ricardo Ribalda Delgado
2019-11-11  4:37   ` Mark Greer
     [not found] <20180930233513.GA16410@animalcreek.com>
2019-11-06 14:13 ` Ricardo Ribalda Delgado

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=20191108090501.GA278603@caravaggio \
    --to=sameo@linux.intel.com \
    --cc=linux-nfc@lists.01.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 read-only IMAP folder(s) and NNTP newsgroup(s).