All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-arch@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] proc: convert everything to "struct proc_ops"
Date: Mon, 6 Jan 2020 18:17:25 +0300	[thread overview]
Message-ID: <20200106151725.GB382@avx2> (raw)
In-Reply-To: <20191231150121.5b09e34205444f6c65277b73@linux-foundation.org>

On Tue, Dec 31, 2019 at 03:01:21PM -0800, Andrew Morton wrote:
> On Wed, 25 Dec 2019 20:25:46 +0300 Alexey Dobriyan <adobriyan@gmail.com> wrote:
> 
> > The most notable change is DEFINE_SHOW_ATTRIBUTE macro split in
> > seq_file.h.
> > 
> > Conversion rule is:
> > 
> > 	llseek		=> proc_lseek
> > 	unlocked_ioctl	=> proc_ioctl
> > 
> > 	xxx		=> proc_xxx
> > 
> > 	delete ".owner = THIS_MODULE" line
> > 
> > ...
> >
> >  drivers/staging/isdn/hysdn/hysdn_procconf.c           |   15 +-
> >  drivers/staging/isdn/hysdn/hysdn_proclog.c            |   17 +-
> 
> These seem to have disappeared in linux-next.

Excellent, the less chunks the better.
Any actual conversion can be dropped if file was deleted.

  reply	other threads:[~2020-01-06 15:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-25 17:22 [PATCH 1/2] proc: decouple proc from VFS with "struct proc_ops" Alexey Dobriyan
2019-12-25 17:25 ` [PATCH 2/2] proc: convert everything to " Alexey Dobriyan
2019-12-31 23:01   ` Andrew Morton
2020-01-06 15:17     ` Alexey Dobriyan [this message]
2021-05-10 13:42   ` youling257
2021-05-10 17:13     ` Alexey Dobriyan
2021-05-10 18:39       ` youling 257

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=20200106151725.GB382@avx2 \
    --to=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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.