From: Kjetil Oftedal <oftedal@gmail.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] sparc64: Expose mdesc to sysfs
Date: Tue, 19 Sep 2017 22:03:30 +0000 [thread overview]
Message-ID: <CALMQjD_mgRb7yPS71RWxbnDsPdHfr7rHLroCtfR8vrqnFx1j0Q@mail.gmail.com> (raw)
In-Reply-To: <201709160508.v8G58BRq011742@aserv0022.oracle.com>
On 19/09/2017, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote:
> On 09/19/2017 10:24 PM, David Miller wrote:
>> davem@patience:~/src/GIT/sparc-next$ dpkg -S /usr/sbin/prtconf
>> sparc-utils: /usr/sbin/prtconf
>>
>> Come again?
>
> David, seriously, are you arguing about Debian packages with me?
>
> sparc-utils is part of the *unreleased* distribution because *I*
> put it there. *unreleased* is *not* an official part of Debian.
>
> sparc-utils is *not* part of Debian unstable.
>
> Adrian
>
Actually, sparc-utils was a part of wheezy/stable before Debian decided
to drop the official SPARC port.
-
Kjetil
next prev parent reply other threads:[~2017-09-19 22:03 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-16 5:08 [PATCH] sparc64: Expose mdesc to sysfs Eric Saint Etienne
2017-09-16 6:08 ` David Miller
2017-09-18 14:23 ` Eric Saint Etienne
2017-09-18 16:43 ` David Miller
2017-09-19 6:43 ` Eric Saint Etienne
2017-09-19 6:53 ` John Paul Adrian Glaubitz
2017-09-19 6:58 ` John Paul Adrian Glaubitz
2017-09-19 15:55 ` Anatoly Pugachev
2017-09-19 17:31 ` David Miller
2017-09-19 17:32 ` David Miller
2017-09-19 17:32 ` David Miller
2017-09-19 17:33 ` David Miller
2017-09-19 17:38 ` John Paul Adrian Glaubitz
2017-09-19 17:40 ` John Paul Adrian Glaubitz
2017-09-19 17:42 ` John Paul Adrian Glaubitz
2017-09-19 18:04 ` David Miller
2017-09-19 18:07 ` David Miller
2017-09-19 18:08 ` John Paul Adrian Glaubitz
2017-09-19 18:10 ` David Miller
2017-09-19 18:12 ` David Miller
2017-09-19 18:14 ` David Miller
2017-09-19 18:39 ` John Paul Adrian Glaubitz
2017-09-19 18:40 ` David Miller
2017-09-19 18:44 ` John Paul Adrian Glaubitz
2017-09-19 18:44 ` John Paul Adrian Glaubitz
2017-09-19 19:16 ` Eric Saint Etienne
2017-09-19 19:43 ` John Paul Adrian Glaubitz
2017-09-19 20:24 ` David Miller
2017-09-19 20:25 ` David Miller
2017-09-19 20:29 ` David Miller
2017-09-19 21:24 ` Anatoly Pugachev
2017-09-19 21:57 ` John Paul Adrian Glaubitz
2017-09-19 22:02 ` John Paul Adrian Glaubitz
2017-09-19 22:03 ` Kjetil Oftedal [this message]
2017-09-19 22:05 ` John Paul Adrian Glaubitz
2017-09-19 22:06 ` David Miller
2017-09-19 22:07 ` David Miller
2017-09-19 22:08 ` David Miller
2017-09-19 22:09 ` John Paul Adrian Glaubitz
2017-09-19 22:12 ` David Miller
2017-09-19 22:13 ` David Miller
2017-09-19 22:13 ` John Paul Adrian Glaubitz
2017-09-19 22:15 ` David Miller
2017-09-19 22:16 ` John Paul Adrian Glaubitz
2017-09-19 22:25 ` John Paul Adrian Glaubitz
2017-09-22 18:40 ` Anatoly Pugachev
2017-09-23 1:35 ` David Miller
2017-09-23 6:14 ` John Paul Adrian Glaubitz
2017-09-23 16:53 ` David Miller
2017-09-23 19:34 ` Frans van Berckel
2017-09-24 16:23 ` Wim Coekaerts
2017-09-24 20:54 ` Eric Saint Etienne
2017-09-25 21:33 ` David Miller
2017-09-29 9:13 ` Eric Saint Etienne
2017-09-29 9:14 ` Eric Saint-Etienne
2017-12-01 17:15 ` Eric Saint Etienne
2017-12-01 19:46 ` David Miller
2017-12-01 20:37 ` Eric Saint Etienne
2017-12-01 21:28 ` David Miller
2017-12-07 16:40 ` Eric Saint Etienne
2017-12-07 18:05 ` David Miller
2017-12-08 8:17 ` Alexandre Chartre
2017-12-14 11:01 ` Eric Saint Etienne
2017-12-14 13:44 ` David Miller
2017-12-14 14:59 ` Eric Saint Etienne
2017-12-14 16:08 ` David Miller
2017-12-14 17:07 ` Xose Vazquez Perez
2017-12-18 19:36 ` David Miller
2017-12-19 18:08 ` Wim Coekaerts
2017-12-19 18:12 ` Mark Cave-Ayland
2017-12-19 18:47 ` john falkenthal
2017-12-19 22:45 ` Greg Onufer
2017-12-20 1:03 ` john falkenthal
2017-12-20 1:12 ` David Miller
2017-12-20 7:34 ` Mark Cave-Ayland
2017-12-20 8:54 ` Frans van Berckel
2017-12-20 18:43 ` David Miller
2018-01-07 22:06 ` Xose Vazquez Perez
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=CALMQjD_mgRb7yPS71RWxbnDsPdHfr7rHLroCtfR8vrqnFx1j0Q@mail.gmail.com \
--to=oftedal@gmail.com \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.