linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-iio <linux-iio@vger.kernel.org>,
	Jonathan Cameron <jic23@kernel.org>,
	Peter Meerwald <pmeerw@pmeerw.net>
Subject: Re: kernel bug tracker
Date: Wed, 9 Dec 2020 18:33:55 +0200	[thread overview]
Message-ID: <CAHp75Vc5b_=KuvJxgxBJgijkKOp_bnbxGo_K04_-svB3oGds5w@mail.gmail.com> (raw)
In-Reply-To: <688821bc-f93c-c98c-974c-ec46fa4111bd@metafoo.de>

On Wed, Dec 9, 2020 at 6:07 PM Lars-Peter Clausen <lars@metafoo.de> wrote:
>
> On 12/9/20 4:58 PM, Andy Shevchenko wrote:
> > Hi!
> >
> > Does the I2O actually refer to IIO on kernel bugzilla?
> > In any case, default there is Alan Cox' email and I didn't find
> > Jonathan's there.
> > If the answer is "yes" for above, does make sense to:
> >   - change its name to IIO
> >   - put mailing list as default assignee?
> >
> >
> There used to be an I2O subsystem, but which has been removed[1].
>
> I supposed if it is used for IIO drivers at the moment I supposed we can
> take over the tag and rename it to IIO, given that there should be no
> new I2O tickets.

Sent request to the help desk.

P.S. I reverted the subsystem to I2O in one bug (#209889) to be able
to filter them out all when we will have a proper component
registered.


--
With Best Regards,
Andy Shevchenko

  reply	other threads:[~2020-12-09 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09 15:58 kernel bug tracker Andy Shevchenko
2020-12-09 16:07 ` Lars-Peter Clausen
2020-12-09 16:33   ` Andy Shevchenko [this message]
2020-12-13 15:15     ` Jonathan Cameron

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='CAHp75Vc5b_=KuvJxgxBJgijkKOp_bnbxGo_K04_-svB3oGds5w@mail.gmail.com' \
    --to=andy.shevchenko@gmail.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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).