From: Jiri Olsa <olsajiri@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] fs: removing unused fops from struct char_device_struct
Date: Thu, 21 Feb 2008 07:08:52 +0100 [thread overview]
Message-ID: <47BD1574.9020705@gmail.com> (raw)
In-Reply-To: <20080221001535.GA23986@kroah.com>
oops, sorry... for some reason I though you were the guy :)
I'll resend
jirka
Greg KH wrote:
> On Wed, Feb 20, 2008 at 09:57:23PM +0100, Jiri Olsa wrote:
>> Hi,
>>
>> seems struct char_device_struct::fops is no longer used, removing it.
>> I checked with "make allyesconfig" and got proper compile.
>>
>> Signed-off-by: Jiri Olsa <olsajiri@gmail.com>
>
> Hm, why send this to me?
>
> Did I make the mistake of touching this file last? Hm, nope, someone
> else touched it after I did, I'm safe :)
>
> Seriously, I have no problem with this, but it should probably go
> through Andrew.
>
> thanks,
>
> greg k-h
>
prev parent reply other threads:[~2008-02-21 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 20:57 [PATCH] fs: removing unused fops from struct char_device_struct Jiri Olsa
2008-02-21 0:15 ` Greg KH
2008-02-21 6:08 ` Jiri Olsa [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=47BD1574.9020705@gmail.com \
--to=olsajiri@gmail.com \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox