linux-kernel - Re: [PATCH 15/21] NTB: Update Version

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130121182604.GE5499@kroah.com>
Date:	Mon, 21 Jan 2013 10:26:04 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Jon Mason <jon.mason@...el.com>
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	Dave Jiang <dave.jiang@...el.com>,
	Nicholas Bellinger <nab@...ux-iscsi.org>
Subject: Re: [PATCH 15/21] NTB: Update Version

On Mon, Jan 21, 2013 at 10:57:41AM -0700, Jon Mason wrote:
> On Sun, Jan 20, 2013 at 03:47:14PM -0800, Greg KH wrote:
> > On Sat, Jan 19, 2013 at 02:02:29AM -0700, Jon Mason wrote:
> > > Update NTB version to 0.25
> > > 
> > > Signed-off-by: Jon Mason <jon.mason@...el.com>
> > > ---
> > >  drivers/ntb/ntb_hw.c |    2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/drivers/ntb/ntb_hw.c b/drivers/ntb/ntb_hw.c
> > > index b792ccd..df86882 100644
> > > --- a/drivers/ntb/ntb_hw.c
> > > +++ b/drivers/ntb/ntb_hw.c
> > > @@ -56,7 +56,7 @@
> > >  #include "ntb_regs.h"
> > >  
> > >  #define NTB_NAME	"Intel(R) PCI-E Non-Transparent Bridge Driver"
> > > -#define NTB_VER		"0.24"
> > > +#define NTB_VER		"0.25"
> > 
> > I'm not objecting to this, but in the end, does it really matter?  Why
> > not just stick with whatever kernel version you are using?  Keeping this
> > up to date is going to be hard over the long haul, right?
> 
> Currently, it is a convenient way to verify the people testing the
> code are running the latest version, since they are usually running
> their tests on a stable kernel.  As the code becomes more stable, I
> can see this becoming unnecessary and I will remove it then.

Ok, that sounds good, thanks.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/