From: Oliver Hartkopp <socketcan@hartkopp.net>
To: David Miller <davem@davemloft.net>, adobriyan@gmail.com
Cc: urs.thuermann@volkswagen.de, oliver.hartkopp@volkswagen.de,
netdev@vger.kernel.org
Subject: Re: [PATCH] can: switch to seq_file
Date: Sat, 29 Aug 2009 10:09:34 +0200 [thread overview]
Message-ID: <4A98E23E.2010009@hartkopp.net> (raw)
In-Reply-To: <20090829.002112.160212045.davem@davemloft.net>
David Miller wrote:
> From: Alexey Dobriyan <adobriyan@gmail.com>
> Date: Fri, 28 Aug 2009 23:57:21 +0400
>
>> create_proc_read_entry() is going to be removed soon.
>>
>> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
>
> Applied to net-next-2.6, thanks.
Good to see that it's obviously ok for Dave ;-)
Many thanks for the effort, Alexey!
I'll do some additional testing when i'm back in the office on Monday.
Tnx & best regards,
Oliver
prev parent reply other threads:[~2009-08-29 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 19:57 [PATCH] can: switch to seq_file Alexey Dobriyan
2009-08-29 7:21 ` David Miller
2009-08-29 8:09 ` Oliver Hartkopp [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=4A98E23E.2010009@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=adobriyan@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=oliver.hartkopp@volkswagen.de \
--cc=urs.thuermann@volkswagen.de \
/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).